From: Greg KH <greg@kroah.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
linux-mtd@lists.infradead.org, stable@kernel.org
Subject: Re: [stable] [Uclinux-dist-devel] [PATCH] mtd: Blackfin NFC: fix build error after nand_scan_ident() change
Date: Fri, 22 Oct 2010 08:54:16 -0700 [thread overview]
Message-ID: <20101022155416.GA18595@kroah.com> (raw)
In-Reply-To: <AANLkTiktR-zNsv4KrnOBh3PxXZTHa6UypzqnwSBpE1=R@mail.gmail.com>
On Sat, Oct 16, 2010 at 05:14:53AM -0400, Mike Frysinger wrote:
> stable team: could you pick this up for 2.6.35.x ?
>
> it has been merged in mainline as eac15a429a27cb74115daaf4c1127c5e854d50e4
But it doesn't apply at all to .35-stable. There is no call to
nand_scan_ident() in that file in the .35 tree.
So, no, sorry, I can't apply it :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-22 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 5:45 [PATCH] mtd: Blackfin NFC: fix build error after nand_scan_ident() change Mike Frysinger
2010-08-30 12:56 ` Artem Bityutskiy
2010-10-16 9:14 ` [Uclinux-dist-devel] " Mike Frysinger
2010-10-22 15:54 ` Greg KH [this message]
2010-10-22 19:42 ` [Uclinux-dist-devel] [stable] " Mike Frysinger
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=20101022155416.GA18595@kroah.com \
--to=greg@kroah.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stable@kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
/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.