Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mgreer@animalcreek.com (Mark A. Greer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] crypto: omap-sham - Fix compile errors when CONFIG_OF not defined
Date: Tue, 15 Jan 2013 16:36:35 -0700	[thread overview]
Message-ID: <20130115233635.GB527@animalcreek.com> (raw)
In-Reply-To: <1358283182-29392-1-git-send-email-mgreer@animalcreek.com>

On Tue, Jan 15, 2013 at 01:53:02PM -0700, Mark A. Greer wrote:
> From: "Mark A. Greer" <mgreer@animalcreek.com>
> 
> Fix the compile errors created by commit 2545e8d
> (crypto: omap-sham - Add Device Tree Support)
> when CONFIG_OF is not defined.  This includes
> changing omap_sham_get_res_dev() to omap_sham_get_res_of()
> and creating an empty version of omap_sham_of_match[].
> 
> Signed-off-by: Mark A. Greer <mgreer@animalcreek.com>
> ---
>  drivers/crypto/omap-sham.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
> index edff981..dc2d354 100644
> --- a/drivers/crypto/omap-sham.c
> +++ b/drivers/crypto/omap-sham.c
> @@ -1607,7 +1607,11 @@ err:
>  	return err;
>  }
>  #else
> -static int omap_sham_get_res_dev(struct omap_sham_dev *dd,
> +static const struct of_device_id omap_sham_of_match[] = {
> +	{},
> +};
> +
> +static int omap_sham_get_res_of(struct omap_sham_dev *dd,
>  		struct device *dev, struct resource *res)
>  {
>  	return -EINVAL;
> -- 
> 1.7.12

I meant to add that this applies to the current cryptodev/master repo/branch.

Mark
--

  reply	other threads:[~2013-01-15 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 20:53 [PATCH] crypto: omap-sham - Fix compile errors when CONFIG_OF not defined Mark A. Greer
2013-01-15 23:36 ` Mark A. Greer [this message]
2013-01-20  0:13 ` Herbert Xu

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=20130115233635.GB527@animalcreek.com \
    --to=mgreer@animalcreek.com \
    --cc=linux-arm-kernel@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