From: Bart.VanAssche@wdc.com (Bart Van Assche)
Subject: [PATCH v2 2/8] crypto: scompress - use sgl_alloc() and sgl_free()
Date: Wed, 1 Nov 2017 15:45:46 +0000 [thread overview]
Message-ID: <1509551145.2530.10.camel@wdc.com> (raw)
In-Reply-To: <CAKv+Gu_-pqqVn5QeuM_OR0itQS-v5uFATt-ZzNDmPy8CHSLrGg@mail.gmail.com>
On Wed, 2017-11-01@15:17 +0000, Ard Biesheuvel wrote:
> On 1 November 2017@14:50, Bart Van Assche <Bart.VanAssche@wdc.com> wrote:
> > On Mon, 2017-10-16@15:49 -0700, Bart Van Assche wrote:
> > > Use the sgl_alloc() and sgl_free() functions instead of open coding
> > > these functions.
> > >
> > > Signed-off-by: Bart Van Assche <bart.vanassche at wdc.com>
> > > Cc: Ard Biesheuvel <ard.biesheuvel at linaro.org>
> > > Cc: Herbert Xu <herbert at gondor.apana.org.au>
> >
> > Ard and/or Herbert, can you please have a look at this patch and let us know
> > whether or not it looks fine to you?
>
> The patch itself does not look unreasonable, but I can't find
> sgl_alloc() anywhere in the source tree. Given that you have cc'ed me
> on this patch only, I can only assume that you are adding this as part
> of the series, but without any context, I can't really review this,
> sorry.
Hello Ard,
Do you expect to be Cc-ed personally or is Cc-ing the linux-crypto mailing
list sufficient? The linux-crypto mailing list was Cc-ed for the entire patch
series as one can see here:
https://www.mail-archive.com/linux-crypto at vger.kernel.org/msg28485.html.
Thanks,
Bart.
next prev parent reply other threads:[~2017-11-01 15:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171016224940.1332-1-bart.vanassche@wdc.com>
[not found] ` <20171016224940.1332-4-bart.vanassche@wdc.com>
2017-10-17 6:07 ` [PATCH v2 3/8] nvmet/fc: Use sgl_alloc() and sgl_free() Hannes Reinecke
[not found] ` <20171016224940.1332-5-bart.vanassche@wdc.com>
2017-10-17 6:08 ` [PATCH v2 4/8] nvmet/rdma: " Hannes Reinecke
[not found] ` <20171016224940.1332-6-bart.vanassche@wdc.com>
2017-10-17 6:14 ` [PATCH v2 5/8] target: Use sgl_alloc_order() " Hannes Reinecke
2017-10-17 14:31 ` Bart Van Assche
[not found] ` <20171016224940.1332-7-bart.vanassche@wdc.com>
2017-10-17 6:19 ` [PATCH v2 6/8] scsi/ipr: Use sgl_alloc_order() and sgl_free_order() Hannes Reinecke
2017-10-18 20:57 ` Brian King
2017-10-30 20:37 ` Bart Van Assche
2017-10-30 21:01 ` Brian King
2017-11-01 11:13 ` Hannes Reinecke
[not found] ` <20171016224940.1332-8-bart.vanassche@wdc.com>
2017-10-17 6:21 ` [PATCH v2 7/8] scsi/pmcraid: Remove an unused structure member Hannes Reinecke
2017-10-17 14:28 ` Bart Van Assche
[not found] ` <20171016224940.1332-9-bart.vanassche@wdc.com>
2017-10-17 6:22 ` [PATCH v2 8/8] scsi/pmcraid: Use sgl_alloc_order() and sgl_free_order() Hannes Reinecke
[not found] ` <20171016224940.1332-2-bart.vanassche@wdc.com>
2017-10-17 6:06 ` [PATCH v2 1/8] lib/scatterlist: Introduce sgl_alloc() and sgl_free() Hannes Reinecke
2017-10-17 9:20 ` Johannes Thumshirn
[not found] ` <20171016224940.1332-3-bart.vanassche@wdc.com>
2017-10-17 6:07 ` [PATCH v2 2/8] crypto: scompress - use " Hannes Reinecke
2017-11-01 14:50 ` Bart Van Assche
2017-11-01 15:17 ` Ard Biesheuvel
2017-11-01 15:45 ` Bart Van Assche [this message]
2017-11-01 15:51 ` Ard Biesheuvel
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=1509551145.2530.10.camel@wdc.com \
--to=bart.vanassche@wdc.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