From: "Michael S. Tsirkin" <mst@redhat.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>
Subject: Re: linux-next: Signed-off-by missing for commit in the vhost tree
Date: Thu, 30 Jul 2020 15:53:06 -0400 [thread overview]
Message-ID: <20200730155043-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200728080556.447ba206@canb.auug.org.au>
On Tue, Jul 28, 2020 at 08:05:56AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> ommit
>
> ed944d574cc7 ("ack! virtio: VIRTIO_F_IOMMU_PLATFORM -> VIRTIO_F_ACCESS_PLATFORM")
>
> is missing a Signed-off-by from its author and committer.
>
> I have never seen an empty commit like this before - I assume it is just
> a way to add an Reviewed-by to a previous commit without rebaseing
> the tree.
Yes - I'm using these to record acks, then squash before the pull
request. git patches I'm using to support this are here - I've rebased
since but didn't have the energy to advocate for upstreaming:
https://lore.kernel.org/r/1460296343-17304-1-git-send-email-mst%40redhat.com
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2020-07-30 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 22:05 linux-next: Signed-off-by missing for commit in the vhost tree Stephen Rothwell
2020-07-30 19:53 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 21:43 Stephen Rothwell
2023-10-18 21:54 ` Michael S. Tsirkin
2023-08-28 5:40 Stephen Rothwell
2023-06-12 23:29 Stephen Rothwell
2023-06-08 22:35 Stephen Rothwell
2022-01-06 21:44 Stephen Rothwell
2020-12-16 10:12 Stephen Rothwell
2019-12-15 20:48 Stephen Rothwell
2019-02-14 20:17 Stephen Rothwell
2019-02-14 20:21 ` Michael S. Tsirkin
2018-01-31 0:14 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=20200730155043-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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).