From: Petr Mladek <pmladek@suse.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: linux-next: Fixes tags need some work in the printk tree
Date: Wed, 2 Sep 2020 09:26:11 +0200 [thread overview]
Message-ID: <20200902072610.GA9496@alley> (raw)
In-Reply-To: <20200902072254.3054db47@canb.auug.org.au>
Hi Stephen,
On Wed 2020-09-02 07:22:54, Stephen Rothwell wrote:
> Hi all,
>
> In commits
>
> e5e4c07d9233 ("docs: vmcoreinfo: add lockless printk ringbuffer vmcoreinfo")
> 0cfdacd74ad5 ("scripts/gdb: update for lockless printk ringbuffer")
>
> Fixes tag
>
> Fixes: ("printk: use the lockless ringbuffer")
The problem is that this commit is not in mainline. It is living
only in printk/linux.git.
>
> has these problem(s):
>
> - No SHA1 recognised
Could we use the SHA1 from the maintainer tree when it would not get rebased?
Or should we rather avoid Fixes: tag referencing commits that are not
in mainline?
I am sorry to bother you with this silly question. I do not see any
hint in Documentation/process/submitting-patches.rst.
Best Regards,
Petr
next prev parent reply other threads:[~2020-09-02 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 21:22 linux-next: Fixes tags need some work in the printk tree Stephen Rothwell
2020-09-02 7:26 ` Petr Mladek [this message]
2020-09-02 20:55 ` Stephen Rothwell
2020-09-03 9:48 ` 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=20200902072610.GA9496@alley \
--to=pmladek@suse.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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