From: Petr Mladek <pmladek@suse.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the printk tree
Date: Wed, 9 Sep 2020 10:16:56 +0200 [thread overview]
Message-ID: <20200909081656.GD3864@alley> (raw)
In-Reply-To: <20200908095924.GA74028@jagdpanzerIV.localdomain>
On Tue 2020-09-08 18:59:24, Sergey Senozhatsky wrote:
> On (20/09/08 09:46), Petr Mladek wrote:
> > On Sat 2020-09-05 12:18:27, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Commit
> > >
> > > 4c31ead75f41 ("printk: ringbuffer: support dataless records")
> > >
> > > is missing a Signed-off-by from its committer.
> >
> > Thanks for catching this. It should be fixed now.
> >
> > It has been originally committed by Sergey. I rebased it to add the
> > missing SHA1[0] and suddenly became committer, see
>
> Oh.
> I missed it somehow that b4/git-am didn't add all the required fields.
> That wasn't the only patch that I applied. So, well.. Sorry and thanks
> for catching and fixing this up.
It was actually my mistake. I should have added my SOB when rebased
the commit.
Best Regards,
Petr
next prev parent reply other threads:[~2020-09-09 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 2:18 linux-next: Signed-off-by missing for commit in the printk tree Stephen Rothwell
2020-09-08 7:46 ` Petr Mladek
2020-09-08 9:59 ` Sergey Senozhatsky
2020-09-09 8:16 ` Petr Mladek [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 22:04 Stephen Rothwell
2020-05-21 11:51 ` Petr Mladek
2018-12-17 20:08 Stephen Rothwell
2018-12-18 8:42 ` 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=20200909081656.GD3864@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.