From: Ard Biesheuvel Subject: Re: [PATCH v2 2/8] crypto: scompress - use sgl_alloc() and sgl_free() Date: Wed, 1 Nov 2017 15:17:06 +0000 Message-ID: References: <20171016224940.1332-1-bart.vanassche@wdc.com> <20171016224940.1332-3-bart.vanassche@wdc.com> <1509547836.2530.1.camel@wdc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: "herbert@gondor.apana.org.au" , "linux-scsi@vger.kernel.org" , "linux-block@vger.kernel.org" , "linux-nvme@lists.infradead.org" , "linux-crypto@vger.kernel.org" , "axboe@kernel.dk" To: Bart Van Assche Return-path: In-Reply-To: <1509547836.2530.1.camel@wdc.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On 1 November 2017 at 14:50, Bart Van Assche wrote: > On Mon, 2017-10-16 at 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 >> Cc: Ard Biesheuvel >> Cc: Herbert Xu > > 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.