[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191011114244.07cf0118@canb.auug.org.au>
Date: Fri, 11 Oct 2019 11:42:44 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Bart Van Assche <bvanassche@....org>
Cc: Jens Axboe <axboe@...nel.dk>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the block tree
Hi Bart,
On Thu, 10 Oct 2019 10:36:36 -0700 Bart Van Assche <bvanassche@....org> wrote:
>
> On 10/7/19 1:16 PM, Stephen Rothwell wrote:
> >
> > Fixes: e34cbd307477 ("blk-wbt: add general throttling mechanism"; v4.10).
>
> The above fixes tag follows the recommended format except that it is
> followed by a kernel version number. Is there a recommended format for
> embedding the kernel version number in a Fixes: tag? I think that
> information is useful. I haven't found any recommendations for how to do
> that in Documentation/process/submitting-patches.rst.
I have not seen any recommended way to do that, but there is no
necessity to embed the version as it can easily be derived:
$ git describe --contains e34cbd307477
v4.10-rc1~153^2~94
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists