From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Redundant kernel patches in the snapshot from20070718
Date: Mon, 30 Jul 2007 22:02:47 +0200 [thread overview]
Message-ID: <20070730200247.GC29064@aon.at> (raw)
In-Reply-To: <20070730192728.GA27993@aon.at>
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.
next prev parent reply other threads:[~2007-07-30 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 14:23 [Buildroot] Redundant kernel patches in the snapshot from 20070718 Hans-Christian Egtvedt
2007-07-26 16:52 ` Ulf Samuelsson
2007-07-27 11:30 ` Bernhard Fischer
2007-07-30 15:51 ` [Buildroot] Redundant kernel patches in the snapshot from20070718 Ulf Samuelsson
2007-07-30 19:27 ` Bernhard Fischer
2007-07-30 20:02 ` Bernhard Fischer [this message]
2007-07-30 23:59 ` Ulf Samuelsson
2007-07-31 8:38 ` Bernhard Fischer
2007-08-01 7:03 ` [Buildroot] Redundant kernel patches in the snapshotfrom20070718 Ulf Samuelsson
2007-07-30 23:53 ` [Buildroot] Redundant kernel patches in the snapshot from20070718 Ulf Samuelsson
2007-07-27 10:59 ` [Buildroot] Redundant kernel patches in the snapshot from 20070718 Bernhard Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070730200247.GC29064@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.