From: David Woodhouse <dwmw2@infradead.org>
To: Anatolij Gustschin <agust@denx.de>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: mpc5121_nfc.c: Fix build failures
Date: Sun, 06 Jun 2010 11:15:08 +0100 [thread overview]
Message-ID: <1275819308.17903.3099.camel@macbook.infradead.org> (raw)
In-Reply-To: <1275323836-15711-1-git-send-email-agust@denx.de>
On Mon, 2010-05-31 at 18:37 +0200, Anatolij Gustschin wrote:
> Fixes build errors caused by the:
> - OF device_node pointer being moved into struct device
> - removal of the match_table field from struct of_platform_driver
>
> Signed-off-by: Anatolij Gustschin <agust@denx.de>
> Cc: Grant Likely <grant.likely@secretlab.ca>
Um, this isn't applicable to 2.6.35, is it?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-06-06 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 16:37 [PATCH] mtd: nand: mpc5121_nfc.c: Fix build failures Anatolij Gustschin
2010-06-06 10:15 ` David Woodhouse [this message]
2010-06-07 7:09 ` Anatolij Gustschin
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=1275819308.17903.3099.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=agust@denx.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).