[Buildroot] Redundant kernel patches in the snapshot from20070718

Ulf Samuelsson ulf at atmel.com
Mon Jul 30 23:59:14 UTC 2007


mån 2007-07-30 klockan 22:02 +0200 skrev Bernhard Fischer:
> On Mon, Jul 30, 2007 at 09:27:28PM +0200, Bernhard Fischer wrote:
> [I deliberately do not correct the gazillions of typos i made]
> 
> >>>>* Cannot apply architecture specific patches, since
> >>>>  you may have conflicts between several patch-set's.
> >>>>* Cluttered directory
> >>> 
> >>> hm? Please explain.
> >>> 
> >>
> >>The AVR32 chips and the AT91 ARM chips uses the same peripherals,
> >>and therefore can use the same drivers.
> >
> >fair enough.
> >
> >So there is _one_ patch which is submitted upstream that is
> >linux-1.2.3.4-add-thisSpecificDevice.patch
> 
> ... where this patch adds _just_ the device. Accompanying
> infrastructure which may be used by a friend class of HW of course has
> to be in a separate patch. This obviously prevents attempts to apply any
> hunk twice, fwiw.

You make the assumption that two different groups
supplying patches actually tests their patches
against the patches for the other group.
Please don't.
Eadch group assumes that their patches are patched
on top of the kernel-patches.
It is the person trying to apply both patchsets 
in the same tree that is causing the error.
Buildroot of today encourages people to apply
patches on top of each other.
If you first build one target and then build another
target in the same tree, then the error occurs...

Your counter argument is that you should use a new tree,
but that is not desirable, so pls use other arguments.

Best Regards
Ulf Samuelsson.





More information about the buildroot mailing list