From: Sunil Muthuswamy <sunilmut@microsoft.com>
To: Borislav Petkov <bp@alien8.de>
Cc: KY Srinivasan <kys@microsoft.com>,
Boqun Feng <Boqun.Feng@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <liuwe@microsoft.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "\"H. Peter Anvin\"" <hpa@zytor.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: RE: [EXTERNAL] Re: [PATCH] Hyper-V: pci: x64: Generalize irq/msi set-up and handling
Date: Thu, 7 Jan 2021 20:16:28 +0000 [thread overview]
Message-ID: <SN4PR2101MB088009D87B77E37943B2F007C0AF9@SN4PR2101MB0880.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20210107080317.GE14697@zn.tnic>
> What is this SoB chain supposed to say?
Quoting from the link you shared:
"The Signed-off-by: tag indicates that the signer was involved in the development of
the patch, or that he/she was in the patch's delivery path."
My intent to include Boqun in the Signed-off by tag was to indicate that he was involved
in the development of the patch here.
- Sunil
next prev parent reply other threads:[~2021-01-07 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 5:05 [PATCH] Hyper-V: pci: x64: Generalize irq/msi set-up and handling Sunil Muthuswamy
2021-01-07 8:03 ` Borislav Petkov
2021-01-07 20:16 ` Sunil Muthuswamy [this message]
2021-01-07 20:21 ` [EXTERNAL] " Borislav Petkov
2021-01-07 20:26 ` Sunil Muthuswamy
2021-01-07 15:02 ` Bjorn Helgaas
2021-01-07 20:20 ` [EXTERNAL] " Sunil Muthuswamy
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=SN4PR2101MB088009D87B77E37943B2F007C0AF9@SN4PR2101MB0880.namprd21.prod.outlook.com \
--to=sunilmut@microsoft.com \
--cc=Boqun.Feng@microsoft.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuwe@microsoft.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mingo@redhat.com \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.