Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, bruce.w.allan@intel.com,
	linux-crypto@vger.kernel.org, qat-linux@intel.com
Subject: Re: [PATCH 1/4] crypto: qat: Fix random config build warnings
Date: Wed, 25 Jun 2014 06:52:16 -0700	[thread overview]
Message-ID: <53AAD410.4090400@intel.com> (raw)
In-Reply-To: <20140625133658.GA10122@gondor.apana.org.au>

On 06/25/2014 06:36 AM, Herbert Xu wrote:
>>  	struct icp_qat_fw_la_resp *qat_resp = resp;
>> >  	struct qat_crypto_request *qat_req =
>> > -			(void *)(dma_addr_t)qat_resp->opaque_data;
>> > +				(void *)(__force long)qat_resp->opaque_data;
> Why not just get rid of the (__force long) altogether?
It complains when cross compiled for 32bit.
Regards.
Tadeusz

  reply	other threads:[~2014-06-25 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 22:19 [PATCH 0/4] crypto: qat: Minor Fixes Tadeusz Struk
2014-06-24 22:19 ` [PATCH 1/4] crypto: qat: Fix random config build warnings Tadeusz Struk
2014-06-25 13:36   ` Herbert Xu
2014-06-25 13:52     ` Tadeusz Struk [this message]
2014-06-26  6:51       ` Herbert Xu
2014-06-24 22:19 ` [PATCH 2/4] crypto: qat: Updated Firmware Info Metadata Tadeusz Struk
2014-06-24 22:19 ` [PATCH 3/4] crypto: qat: Fixed new checkpatch warnings Tadeusz Struk
2014-06-24 22:19 ` [PATCH 4/4] crypto: qat: Fix error path crash when no firmware is present Tadeusz Struk

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=53AAD410.4090400@intel.com \
    --to=tadeusz.struk@intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=qat-linux@intel.com \
    /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