From: Joe Perches <joe@perches.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: make sure swap arguments are the same type? (was: Re: [PATCH] crypto: rmd320 - use swap macro in rmd320_transform)
Date: Fri, 20 Jul 2018 22:34:56 -0700 [thread overview]
Message-ID: <085e361269db5f5f923a65a52e1000d5cd79eee4.camel@perches.com> (raw)
In-Reply-To: <ac6bf6b3-b739-a6b8-c9b0-8d496fb7a470@embeddedor.com>
On Fri, 2018-07-20 at 10:43 -0500, Gustavo A. R. Silva wrote:
> Hi Joe,
>
> I like the idea. I'll take a look at the cases you mention and see
> if I can make them work with your version of swap.
>
> BTW, I wonder if it would be more convenient to trigger a build warning
> instead of an error.
>
> What do you think?
I can't think of a way to have a #pragma (or _Pragma equivalent)
emit a warning on a condition.
next prev parent reply other threads:[~2018-07-21 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 17:19 [PATCH] crypto: rmd320 - use swap macro in rmd320_transform Gustavo A. R. Silva
2018-07-18 18:31 ` make sure swap arguments are the same type? (was: Re: [PATCH] crypto: rmd320 - use swap macro in rmd320_transform) Joe Perches
2018-07-20 15:43 ` Gustavo A. R. Silva
2018-07-21 5:34 ` Joe Perches [this message]
2018-07-27 16:05 ` [PATCH] crypto: rmd320 - use swap macro in rmd320_transform 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=085e361269db5f5f923a65a52e1000d5cd79eee4.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gustavo@embeddedor.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pablo@netfilter.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
all inboxes | Powered by JetHome®