From: Sergey Senozhatsky <sergey.senozhatsky@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: John Ogness <john.ogness@linutronix•de>,
Petr Mladek <pmladek@suse•com>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail•com>
Subject: Re: linux-next: Fixes tag needs some work in the printk tree
Date: Tue, 28 Jul 2020 10:22:57 +0900 [thread overview]
Message-ID: <20200728012257.GA1282472@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20200728081959.2df754d0@canb.auug.org.au>
On (20/07/28 08:19), Stephen Rothwell wrote:
> On Mon, 27 Jul 2020 17:13:44 +0206 John Ogness <john.ogness@linutronix•de> wrote:
> >
> > On 2020-07-27, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
[..]
> > > Maybe you meant
> > >
> > > Fixes: 896fbe20b4e2 ("printk: use the lockless ringbuffer")
> >
> > Yes, sorry. I did not think linux-next SHA1 hashes were used in commit
> > logs.
Neither did I. The tag made sense to me, because it fixes a regression
after all.
> Well, it makes sense to use them if they are stable (i.e. the tree they
> are in does not rebase) which, by this part of the cycle, I would
> *hope* would be true (but sometimes isn't :-().
So we probably should not have Fixes tags in linux-next commits
(printk rework branch) then, for the time being. I'll keep an eye
on that.
-ss
next prev parent reply other threads:[~2020-07-28 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:46 linux-next: Fixes tag needs some work in the printk tree Stephen Rothwell
2020-07-27 15:07 ` John Ogness
2020-07-27 22:19 ` Stephen Rothwell
2020-07-28 1:22 ` Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-23 21:53 Stephen Rothwell
2025-11-24 14:54 ` Petr Mladek
2021-07-11 3:01 Stephen Rothwell
2020-11-02 21:32 Stephen Rothwell
2020-11-03 8:46 ` Petr Mladek
2019-04-25 13:30 Stephen Rothwell
2019-04-26 7:37 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200728012257.GA1282472@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail$(echo .)com \
--cc=john.ogness@linutronix$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pmladek@suse$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox