All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the device-mapper tree
Date: Wed, 18 Nov 2020 16:19:57 -0500	[thread overview]
Message-ID: <20201118211957.GA2203@redhat.com> (raw)
In-Reply-To: <20201119074717.79d94aba@canb.auug.org.au>

On Wed, Nov 18 2020 at  3:47pm -0500,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> Commit
> 
>   a1e4865b4dda ("dm writecache: remove BUG() and fail gracefully instead")
> 
> is missing a Signed-off-by from its author.

Thanks, because I went in a different direction on the code changes I
adjusted author via rebase in my local branch to be me.. but when I
pushed it, it reverted back to being Randy as author on the remote
branch. Turns out the rebase needed to be --continue'd.

Anyway, it should be all set now.

Thanks,
Mike


  reply	other threads:[~2020-11-18 21:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 20:47 linux-next: Signed-off-by missing for commit in the device-mapper tree Stephen Rothwell
2020-11-18 21:19 ` Mike Snitzer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-11 22:38 Stephen Rothwell
2024-07-08  8:20 Stephen Rothwell
2024-07-08 13:00 ` Mikulas Patocka
2024-03-12 21:05 Stephen Rothwell
2024-03-03 22:15 Stephen Rothwell
2023-11-29 20:36 Stephen Rothwell
2021-05-26 21:59 Stephen Rothwell
2018-12-06 22:47 Stephen Rothwell
2018-01-25 11:15 Stephen Rothwell
2018-01-15 13:27 Stephen Rothwell

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=20201118211957.GA2203@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.