From: David Miller <davem@davemloft.net>
To: agust@denx.de
Cc: linux-crypto@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
herbert@gondor.apana.org.au
Subject: Re: [PATCH] of/crypto: n2_core.c: Fix build failures
Date: Wed, 02 Jun 2010 19:45:49 -0700 (PDT) [thread overview]
Message-ID: <20100602.194549.200117567.davem@davemloft.net> (raw)
In-Reply-To: <1275521741-11040-1-git-send-email-y>
From: agust@denx.de
Date: Thu, 3 Jun 2010 01:35:41 +0200
> From: Anatolij Gustschin <agust@denx.de>
>
> Fixes build errors caused by the:
> - OF device_node pointer being moved into struct device
> - removal of the match_table and name fields from
> struct of_platform_driver
>
> Signed-off-by: Anatolij Gustschin <agust@denx.de>
This is already fixed in the crypto GIT tree.
next prev parent reply other threads:[~2010-06-03 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1275521741-11040-1-git-send-email-y>
2010-06-03 2:11 ` [PATCH] of/crypto: n2_core.c: Fix build failures Grant Likely
2010-06-03 2:45 ` David Miller [this message]
2010-06-03 3:00 ` Grant Likely
2010-06-02 23:35 y
-- strict thread matches above, loose matches on Subject: below --
2010-06-02 23:35 y
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=20100602.194549.200117567.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=agust@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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