From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-f67.google.com ([209.85.216.67]:37133 "EHLO mail-pj1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725819AbfKUCGT (ORCPT ); Wed, 20 Nov 2019 21:06:19 -0500 Received: by mail-pj1-f67.google.com with SMTP id f3so716843pjg.4 for ; Wed, 20 Nov 2019 18:06:19 -0800 (PST) Subject: Re: [PATCH -next] writeback: fix -Wformat compilation warnings References: <20191114192118.GK4163745@devbig004.ftw2.facebook.com> <9D52EBB0-BE48-4C59-9145-857C3247B20D@lca.pw> <20191115145540.GP4163745@devbig004.ftw2.facebook.com> <1574279778.9585.15.camel@lca.pw> From: Jens Axboe Message-ID: <26dc5699-9223-3e35-65f3-955fef7a990a@kernel.dk> Date: Wed, 20 Nov 2019 16:17:51 -0700 MIME-Version: 1.0 In-Reply-To: <1574279778.9585.15.camel@lca.pw> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-s390-owner@vger.kernel.org List-ID: To: Qian Cai , Tejun Heo , Andrew Morton Cc: jack@suse.cz, gregkh@linuxfoundation.org, cgroups@vger.kernel.org, heiko.carstens@de.ibm.com, gor@linux.ibm.com, borntraeger@de.ibm.com, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org On 11/20/19 12:56 PM, Qian Cai wrote: > On Fri, 2019-11-15 at 06:55 -0800, Tejun Heo wrote: >> On Thu, Nov 14, 2019 at 07:26:21PM -0500, Qian Cai wrote: >>> >>> >>>> On Nov 14, 2019, at 2:21 PM, Tejun Heo wrote: >>>> >>>> Acked-by: Tejun Heo >>> >>> Tejun, suppose you will take this patch via your tree together with the series or should I Cc Andrew who normally handle this file? >> >> Patches in this area usually goes through Jens's block tree. > > I remember that last time Jens had no interests in picking up trivial patches > like this one. See the commit d1a445d3b86c ("include/trace/events/writeback.h: > fix -Wstringop-truncation warnings"). > > Andrew, care to pick up this again? > > https://lore.kernel.org/lkml/1573751861-10303-1-git-send-email-cai@lca.pw/ I'm fine with picking it up, this one isn't trivial and it's fixing warnings. But I didn't (and don't) carry f05499a06fb4 in my tree, so it'd be more logical to funnel this one through the tree that has the offending commit. -- Jens Axboe