Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] target/device/KwikByte/kb9202/kernel-patches/linux-2.6.26-rc3-at91.patch.gz
Date: Fri, 08 Aug 2008 17:00:51 -0700	[thread overview]
Message-ID: <1218240051.6306.23.camel@kokopelli> (raw)

I'm working on upgrading kb9202 support to the 2.6.26 kernel and have
found that this patchfile has a slight problem against the 2.6.26 kernel
sources in that it contains a patch of drivers/mmc/host/at91_mci.c that
does not apply as the fix it contains has already been made.  I have a
modified copy of the patchfile with that patch removed.  I don't know if
anybody is interested.
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?

Brian Beattie   LFS12947 | "Honor isn't about making the right choices.
beattie at beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net     | -- Midori Koto

                 reply	other threads:[~2008-08-09  0:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1218240051.6306.23.camel@kokopelli \
    --to=beattie@beattie-home.net \
    --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