From: Herbert Xu <herbert@gondor.apana.org.au>
To: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Cc: Liu Shixin <liushixin2@huawei.com>,
"David S . Miller" <davem@davemloft.net>,
qat-linux <qat-linux@intel.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] crypto: qat - convert to use DEFINE_SEQ_ATTRIBUTE macro
Date: Fri, 25 Sep 2020 18:14:45 +1000 [thread overview]
Message-ID: <20200925081445.GA6496@gondor.apana.org.au> (raw)
In-Reply-To: <20200924050042.GA32206@silpixa00400314>
On Thu, Sep 24, 2020 at 06:00:42AM +0100, Giovanni Cabiddu wrote:
> On Wed, Sep 16, 2020 at 03:50:17AM +0100, Liu Shixin wrote:
> > Use DEFINE_SEQ_ATTRIBUTE macro to simplify the code.
> >
> > Signed-off-by: Liu Shixin <liushixin2@huawei.com>
>
> Acked-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Hi Giovanni:
Your acks are not making it to patchwork, seemingly because your
emails have a bogus References header with an Intel message ID
instead of the original message ID of the email you're replying
to.
I've added your acks manually for this patch but please fix your
emails as I can't guarantee that I'll spot the problem every time.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2020-09-25 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7a1e8142cb4944ee95cea13e7efad23d@irsmsx602.ger.corp.intel.com>
2020-09-24 5:00 ` [PATCH -next] crypto: qat - convert to use DEFINE_SEQ_ATTRIBUTE macro Giovanni Cabiddu
2020-09-25 8:14 ` Herbert Xu [this message]
2020-09-25 8:49 ` Giovanni Cabiddu
2020-09-16 2:50 Liu Shixin
2020-09-25 8:11 ` 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=20200925081445.GA6496@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=giovanni.cabiddu@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--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