Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751434AbdIKL52 (ORCPT ); Mon, 11 Sep 2017 07:57:28 -0400 Received: from verein.lst.de ([213.95.11.211]:45977 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750965AbdIKL50 (ORCPT ); Mon, 11 Sep 2017 07:57:26 -0400 Date: Mon, 11 Sep 2017 13:57:25 +0200 From: Christoph Hellwig To: Martin Wilck Cc: Stephen Rothwell , Christoph Hellwig , Sagi Grimberg , Kees Cook , linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, Jens Axboe , Andrew Morton , linux-nvme@lists.infradead.org, jthumshirn@suse.com, arnd@arndb.de Subject: Re: [PATCH] string.h: un-fortify memcpy_and_pad Message-ID: <20170911115725.GB21472@lst.de> References: <20170831182101.0e4ad9a2@canb.auug.org.au> <20170906123657.25534-1-mwilck@suse.com> <1505123078.4683.5.camel@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1505123078.4683.5.camel@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 441 Lines: 10 > Hello Stephen and Christoph, > > my broken patch 01f33c336e2d is in Linus' tree and causing compiler > warnings there. Could you please take care that this fix is pulled in > on top of it? Or should I take another action myself? string.h is a bit of a maintainers no mans land. Given that the problematic commit came in through the nvme tree I've applied your patch and will sned it to Jens with the next batch of nvme updates tonight.