From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bump kernel headers to latest stable, including scsi patch for latests kernel headers
Date: Mon, 06 Sep 2010 09:37:47 +0200 [thread overview]
Message-ID: <87fwxntj90.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1283626182-28176-1-git-send-email-marcus.osdoba@googlemail.com> (Marcus Osdoba's message of "Sat, 4 Sep 2010 20:49:42 +0200")
>>>>> "Marcus" == Marcus Osdoba <marcus.osdoba@googlemail.com> writes:
Marcus> bump to latest (begin of September 2010) kernel headers,
Thanks, but something seems to have gotten wrong, git am cannot apply
it. I've made the bump myself and at the same time removed
2.6.27/2.6.28.
Marcus> scsi.h and scsi_net.h have not changed since April 2010
Marcus> so renaming the scsi patches files in toolchain/kernel-headers/
Marcus> to match higher versions
Yeah, the fix is finally in mainline for 2.6.36.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-09-06 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 18:49 [Buildroot] [PATCH] bump kernel headers to latest stable, including scsi patch for latests kernel headers Marcus Osdoba
2010-09-04 20:36 ` Marcus Osdoba
2010-09-06 7:37 ` Peter Korsgaard [this message]
2010-09-06 7:50 ` Marcus Osdoba
2010-09-06 8:03 ` Peter Korsgaard
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=87fwxntj90.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox