From: Jens Axboe <axboe@kernel•dk>
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>
Subject: Re: linux-next: Signed-off-by missing for commit in the block tree
Date: Sun, 5 Aug 2018 19:16:56 -0600 [thread overview]
Message-ID: <91bc0348-fbb4-168b-2946-5163a204819b@kernel.dk> (raw)
In-Reply-To: <20180806075112.6253d2da@canb.auug.org.au>
On 8/5/18 3:51 PM, Stephen Rothwell wrote:
> Hi Jens,
>
> Commit
>
> 290a40cb336c ("nvme: don't enable AEN if not supported")
>
> is missing a Signed-off-by from its committer.
It's because I'm an idiot and cherry picked the commit. Not only is
it missing the SOB, but it'll also show up twice if pulled. I'll likely
just have to rebase to get rid of this, and then pull in the right
-rc instead... Will do that tomorrow.
--
Jens Axboe
next prev parent reply other threads:[~2018-08-06 1:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 21:51 linux-next: Signed-off-by missing for commit in the block tree Stephen Rothwell
2018-08-06 1:16 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-16 6:26 Stephen Rothwell
2018-12-16 10:18 ` Christoph Hellwig
2018-12-16 15:33 ` Jens Axboe
2019-05-22 21:50 Stephen Rothwell
2019-05-22 23:26 ` Jens Axboe
2020-04-08 21:59 Stephen Rothwell
2020-06-26 23:08 Stephen Rothwell
2020-12-02 20:52 Stephen Rothwell
2021-01-25 9:43 Stephen Rothwell
2021-01-25 15:18 ` Jens Axboe
2021-03-04 23:54 Stephen Rothwell
2021-03-18 23:16 Stephen Rothwell
2021-03-18 23:25 ` Jens Axboe
2021-03-19 8:02 ` Stefan Metzmacher
2021-03-19 13:08 ` Jens Axboe
2021-03-19 13:10 ` Stefan Metzmacher
2021-04-11 22:34 Stephen Rothwell
2021-04-12 2:14 ` Jens Axboe
2021-04-12 2:26 ` Sowjanya Komatineni
2021-04-12 2:36 ` Jens Axboe
2021-06-08 22:31 Stephen Rothwell
2021-08-10 21:58 Stephen Rothwell
2022-03-29 21:11 Stephen Rothwell
2022-03-30 5:00 ` Christoph Hellwig
2022-07-20 13:16 Stephen Rothwell
2022-07-20 13:21 ` Christoph Hellwig
2022-07-20 15:58 ` Jens Axboe
2023-01-22 21:08 Stephen Rothwell
2023-01-22 21:30 ` Jens Axboe
2023-01-22 21:34 ` Stephen Rothwell
2023-01-22 21:37 ` Jens Axboe
2024-09-08 22:03 Stephen Rothwell
2024-09-09 22:06 Stephen Rothwell
2024-09-09 22:12 ` Jens Axboe
2025-01-12 20:51 Stephen Rothwell
2025-01-12 22:00 ` Jens Axboe
2025-06-05 21:52 Stephen Rothwell
2025-06-05 21:55 ` Jens Axboe
2025-06-05 22:00 ` Keith Busch
2025-06-05 21:57 ` Keith Busch
2025-06-05 22:04 ` Jens Axboe
2025-06-09 4:13 ` Christoph Hellwig
2025-11-18 21:48 Stephen Rothwell
2025-11-18 21:59 ` Jens Axboe
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=91bc0348-fbb4-168b-2946-5163a204819b@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--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