[PATCH v3 0/10] sh_flctl hardware ECC mode cleanup

[Bastian Hecht]

2012/5/2 Artem Bityutskiy <dedekind1 at gmail.com>:
> On Wed, 2012-05-02 at 15:41 +0200, Bastian Hecht wrote:
>> Ok I'm slowly but surely fighting my way through it. Though I want to
>> add an advisor here:
>> Don't do this on your crappy laptop like I do. I guess I will move to
>> my 8Gb RAM desktop machine for this in the future ;)
>
> Yeah, I run it on a powerful PC. I need to update the README file - but
> if you send a patch - will be appreciated.

I assumed people to be smarter than me and instantly realize that a
compile-test is resource intensive, so I'm unsure if this is
necessary.

>> There's only 1 thing I don't completely grasp: you pass a target path
>> to aiaiai/test-patchset and a working tree. I didn't manage to get it
>> take the l2_mackerel_defconfig from one and compile the patches on top
>> of the other.
>
> Yeah, this is in my TODO list to teach aiaiai to take defconfig files
> which are not part of the tree. So you basically need to copy the
> l2-mackerel_defconfig file to your tree and commit it, so that the
> defconfig is part of the git tree you are testing against.
>
> But I want to teach test-patchset to accept just stand-along defconfig
> files.
>
> The reason it is implemented the way it is implemented because it was
> originally done for an internal project where we have a couple of
> defconfigs which are part of the project tree.
>
>>  So I simply copied the defconfig to my kernel dir and
>> ran the command manually.
>
> You should also commit it, of course. Because the way aiaiai works it
> first clones your tree and then work with the clone. This is done to
> make sure your tree is preserved intact.
>

Ok, then I completely understood the concept. In fact I did commit the
defconfig after I used verbose output and saw the clones of the trees.
But I must admit that I'm still struggling to get the same warnings
from your post. But I'll manage I guess.

> --
> Best Regards,
> Artem Bityutskiy