From: Ingo Molnar <mingo@kernel.org>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the tip tree
Date: Wed, 23 Oct 2019 12:16:03 +0200 [thread overview]
Message-ID: <20191023101603.GA120912@gmail.com> (raw)
In-Reply-To: <MN2PR05MB6141177C37F2D1566E4FB341A1680@MN2PR05MB6141.namprd05.prod.outlook.com>
* Thomas Hellstrom <thellstrom@vmware.com> wrote:
> On 10/22/19 10:17 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > n commit
> >
> > 6fee2a0be0ec ("x86/cpu/vmware: Fix platform detection VMWARE_PORT macro")
> >
> > Fixes tag
> >
> > Fixes: b4dd4f6e3648 ("Add a header file for hypercall definitions")
>
> The cited subject is missing a leading "x86/vmware:". Ingo, please let
> me know if you want me to respin those.
Those who are picking it up for a backport will go by the sha1, while
humans reading it are fine without the prefix, I think this is OK as-is.
Thanks,
Ingo
next prev parent reply other threads:[~2019-10-23 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 20:16 linux-next: Fixes tags need some work in the tip tree Stephen Rothwell
2019-10-22 20:30 ` Thomas Hellstrom
2019-10-23 10:16 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-05 11:18 Stephen Rothwell
2019-11-05 11:52 ` Thomas Gleixner
2020-01-15 20:03 Stephen Rothwell
2021-03-08 2:16 Stephen Rothwell
2021-03-08 8:38 ` Ingo Molnar
2024-07-21 22:31 Stephen Rothwell
2024-07-23 11:02 ` Marc Zyngier
2024-07-26 12:04 ` Thomas Gleixner
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=20191023101603.GA120912@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=thellstrom@vmware.com \
/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.