From: Bjorn Helgaas <helgaas@kernel.org>
To: Frank Li <frank.li@nxp.com>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
<linux-pci@vger.kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"M.H. Lian" <minghuan.lian@nxp.com>,
"moderated list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
<linux-arm-kernel@lists.infradead.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Roy Zang" <roy.zang@nxp.com>,
"open list:PCI DRIVER FOR FREESCALE LAYERSCAPE"
<linuxppc-dev@lists.ozlabs.org>, "Rob Herring" <robh@kernel.org>,
"Mingkai Hu" <mingkai.hu@nxp.com>
Subject: Re: [EXT] Re: [PATCH v2 1/1] PCI: layerscape: Add the endpoint linkup notifier support
Date: Tue, 9 May 2023 14:44:06 -0500 [thread overview]
Message-ID: <20230509194406.GA1265845@bhelgaas> (raw)
In-Reply-To: <AM6PR04MB4838C21F4C2F0689B13B05A988719@AM6PR04MB4838.eurprd04.prod.outlook.com>
On Mon, May 08, 2023 at 09:45:59PM +0000, Frank Li wrote:
> > > > Subject: [EXT] Re: [PATCH v2 1/1] PCI: layerscape: Add the endpoint
> > linkup
> > > > notifier support
> >
> > All these quoted headers are redundant clutter since we've already
> > seen them when Manivannan sent his comments. It would be nice if your
> > mailer could be configured to omit them.
>
> Our email client quite stupid.
Yeah, sometimes those are really hard to work around.
Bjorn
prev parent reply other threads:[~2023-05-09 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 14:48 [PATCH v2 1/1] PCI: layerscape: Add the endpoint linkup notifier support Frank Li
2023-05-06 7:58 ` Manivannan Sadhasivam
2023-05-08 13:31 ` [EXT] " Frank Li
2023-05-08 21:31 ` Bjorn Helgaas
2023-05-08 21:45 ` Frank Li
2023-05-09 19:44 ` Bjorn Helgaas [this message]
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=20230509194406.GA1265845@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=minghuan.lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=robh@kernel.org \
--cc=roy.zang@nxp.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 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).