linux-kernel - Re: linux-next: Fixes tags need some work in the printk tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200902072610.GA9496@alley>
Date:   Wed, 2 Sep 2020 09:26:11 +0200
From:   Petr Mladek <pmladek@...e.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        John Ogness <john.ogness@...utronix.de>
Subject: Re: linux-next: Fixes tags need some work in the printk tree

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