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>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: linux-next: Fixes tags need some work in the printk tree
Date: Thu, 3 Sep 2020 11:48:37 +0200 [thread overview]
Message-ID: <20200903091436.GA5012@alley> (raw)
In-Reply-To: <20200903065547.0cc6f53b@canb.auug.org.au>
On Thu 2020-09-03 06:55:47, Stephen Rothwell wrote:
> Hi Petr,
>
> On Wed, 2 Sep 2020 09:26:11 +0200 Petr Mladek <pmladek@suse.com> wrote:
> >
> > The problem is that this commit is not in mainline. It is living
> > only in printk/linux.git.
> >
> > 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.
>
> Well, in theory, maintainers trees should not be rebased after they
> have been published (except in exceptional circumstances), so using
> SHA1s from them should be OK. Especially if the fixing commit is in
> the same maintainers tree (which it should be, right). It does mean
> that maintainers need to be a bit more careful if they do rebase their
> trees to update any Fixes tags (or other commit references) that are
> affected by the rebase.
Thanks a lot for info.
I have rebased the last 5 commits in the printk-rework branch and
added the missing SHAs there.
Best Regards,
Petr
prev parent reply other threads:[~2020-09-03 9:48 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
2020-09-02 20:55 ` Stephen Rothwell
2020-09-03 9:48 ` Petr Mladek [this message]
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=20200903091436.GA5012@alley \
--to=pmladek@suse.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).