Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3811603pxb; Tue, 26 Jan 2021 05:33:20 -0800 (PST) X-Google-Smtp-Source: ABdhPJzOf+DGE+D+H12tfSDyDth9niAwaN1uVCfbTXIOvgbEbhlWgXApzCvljibg6usDg2YyOnlY X-Received: by 2002:a05:6402:430c:: with SMTP id m12mr4804335edc.299.1611668000355; Tue, 26 Jan 2021 05:33:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611668000; cv=none; d=google.com; s=arc-20160816; b=hEGy2oStywUDX5RiqOcH1Tiq5g9ItMGX1ApctjijaFR3PEXf3Qv3lzdqQxiH2dPuc0 e10lcayphH3lHOFR4/jKjd2lE2CY+MVmVgIf8MQwXHHIO7U1jGiyz0NnOadzfD1PnB3F b0G1s5FMiJrVF+EOARiAFG4e5MlckLdcK/LFDJOp7s/cWwaIASGbR5yryMHyxNl+YmBB 1ohK4wgZtbq8NnFVupG1dAYCNT3OhJ6vKpTdvlE2NFYxGvH2jnLmH7eO9QCWxl5ScA2M 4D2hfSn3cGpSnSMS63+HuYekKgtTZ/WxWTjJ7bT0VIJu72KZizfP28n87ZARUTTSQFva BGuA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=iaI/raUPgMn7hMsVBquC6oWCbyGlu/q4wc8bSzs3rPA=; b=wFvnQmJIu1nD+C42wxxCv3ZOatxsc6/mNaSc89fOIpeHsE+XKHjfD3DbWYSMoaW0OP +eCtL7OIZyTCGjnijQ2+Dy/MEaF1yWrLtsfZGXskerEn/FIJE1cfTFElWxjW5b5/U1fa b39jxOhCFAwhiOwl6ybTWxoh09Sk2Vs4uMUECTagUxZF/jtt8z9Xghzh+niQlw0aRZKJ 6Hx5D2jqIFpwVzFtbKr7da78ggKp0aENRSNQzNq/Iui2gfa7oI4cPKPws/SmQIL00aU1 0uXmssoLSCsn3dKm1Z1b3U9o4aRJOnoGn+rlws/Nag6oBRg3U8uY8+0qAPsZhgscJHUj Rsyw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z9si7019817eja.51.2021.01.26.05.32.55; Tue, 26 Jan 2021 05:33:20 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391754AbhAZNbL (ORCPT + 99 others); Tue, 26 Jan 2021 08:31:11 -0500 Received: from mx2.suse.de ([195.135.220.15]:59872 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404486AbhAZNa2 (ORCPT ); Tue, 26 Jan 2021 08:30:28 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id E6FA5AD6B; Tue, 26 Jan 2021 13:29:46 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 50C1C1E151D; Tue, 26 Jan 2021 14:29:46 +0100 (CET) Date: Tue, 26 Jan 2021 14:29:46 +0100 From: Jan Kara To: Jens Axboe Cc: Paolo Valente , Stephen Rothwell , Jia Cheng Hu , Jan Kara , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: Fixes tag needs some work in the block tree Message-ID: <20210126132946.GC10966@quack2.suse.cz> References: <20210125204032.6b6a604b@canb.auug.org.au> <3F91181A-EDF2-4F01-9839-17B40D6EA07F@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 25-01-21 11:39:50, Jens Axboe wrote: > On 1/25/21 11:35 AM, Paolo Valente wrote: > > > > > >> Il giorno 25 gen 2021, alle ore 10:40, Stephen Rothwell ha scritto: > >> > >> Hi all, > >> > >> In commit > >> > >> d4fc3640ff36 ("block, bfq: set next_rq to waker_bfqq->next_rq in waker injection") > >> > >> Fixes tag > >> > >> Fixes: c5089591c3ba ("block, bfq: detect wakers and unconditionally inject their I/O") > >> > >> has these problem(s): > >> > >> - Target SHA1 does not exist > >> > >> Maybe you meant > >> > >> Fixes: 13a857a4c4e8 ("block, bfq: detect wakers and unconditionally inject their I/O") > >> > > > > Hi Jens, > > how to proceed in such a case (with patches already applied by you)? > > Shall I send you a v2 with only this change? > > We just have to ignore it... But in the future, always double check that > you are using the right shas, not some sha from an internal tree. FWIW I have a commit hook in my git tree that just refuses a commit with unknown Fixes tag SHA. Exactly to catch such mishaps in the patches I merge... Honza -- Jan Kara SUSE Labs, CR