From: Bjorn Helgaas <helgaas@kernel.org>
To: Xiaochun XC17 Li <lixc17@lenovo.com>
Cc: kernel test robot <lkp@intel.com>,
Xiaochun Lee <lixiaochun.2888@163.com>,
"nirmal.patel@linux.intel.com" <nirmal.patel@linux.intel.com>,
"jonathan.derrick@linux.dev" <jonathan.derrick@linux.dev>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"kw@linux.com" <kw@linux.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH v1] PCI: Set no io resource for bridges that behind VMD controller
Date: Tue, 27 Sep 2022 10:52:03 -0500 [thread overview]
Message-ID: <20220927155203.GA1704003@bhelgaas> (raw)
In-Reply-To: <SEYPR03MB6877EF05F0F1320B6EE0B9F9BC559@SEYPR03MB6877.apcprd03.prod.outlook.com>
On Tue, Sep 27, 2022 at 02:40:39AM +0000, Xiaochun XC17 Li wrote:
> On Sun, Sep 25, 2022 at 8:57 PM +0800, Bjorn Helgaas <helgaas@kernel.org> wrote:
> > On Sun, Sep 25, 2022 at 09:52:21AM +0000, Xiaochun XC17 Li wrote:
> > > > -----Original Message-----
> > > > From: kernel test robot <lkp@intel.com>
> > > > Sent: Friday, September 23, 2022 11:21 PM
> > > > To: Xiaochun Lee <lixiaochun.2888@163.com>;
> > > > nirmal.patel@linux.intel.com; jonathan.derrick@linux.dev
> > > > Cc: kbuild-all@lists.01.org; lpieralisi@kernel.org; robh@kernel.org;
> > > > kw@linux.com; bhelgaas@google.com; linux-pci@vger.kernel.org;
> > linux-
> > > > kernel@vger.kernel.org; Xiaochun XC17 Li <lixc17@lenovo.com>
> > > > Subject: [External] Re: [PATCH v1] PCI: Set no io resource for
> > > > bridges that behind VMD controller
> > ...
> > For future reference, your email reply doesn't follow the usual Linux
> > mailing list style, so it is unnecessarily hard to read. In particular, it lacks
> > the line that shows what you're responding to.
> > It would look something like this:
> >
> > On Fri, Sep 23, 2022 at 11:21PM +0800, kernel test robot wrote:
>
> OK, thanks!
> I did a test just now, it seems to meet the format requirements.
> I sent emails via outlook, and I've tried to set the reply format,
> unfortunately, the time zone and date time are not resolved correctly.
Much better, thanks! It's much easier to read without all the
redundant headers.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [External] Re: [PATCH v1] PCI: Set no io resource for bridges that behind VMD controller
Date: Tue, 27 Sep 2022 10:52:03 -0500 [thread overview]
Message-ID: <20220927155203.GA1704003@bhelgaas> (raw)
In-Reply-To: <SEYPR03MB6877EF05F0F1320B6EE0B9F9BC559@SEYPR03MB6877.apcprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
On Tue, Sep 27, 2022 at 02:40:39AM +0000, Xiaochun XC17 Li wrote:
> On Sun, Sep 25, 2022 at 8:57 PM +0800, Bjorn Helgaas <helgaas@kernel.org> wrote:
> > On Sun, Sep 25, 2022 at 09:52:21AM +0000, Xiaochun XC17 Li wrote:
> > > > -----Original Message-----
> > > > From: kernel test robot <lkp@intel.com>
> > > > Sent: Friday, September 23, 2022 11:21 PM
> > > > To: Xiaochun Lee <lixiaochun.2888@163.com>;
> > > > nirmal.patel(a)linux.intel.com; jonathan.derrick(a)linux.dev
> > > > Cc: kbuild-all(a)lists.01.org; lpieralisi(a)kernel.org; robh(a)kernel.org;
> > > > kw(a)linux.com; bhelgaas(a)google.com; linux-pci(a)vger.kernel.org;
> > linux-
> > > > kernel(a)vger.kernel.org; Xiaochun XC17 Li <lixc17@lenovo.com>
> > > > Subject: [External] Re: [PATCH v1] PCI: Set no io resource for
> > > > bridges that behind VMD controller
> > ...
> > For future reference, your email reply doesn't follow the usual Linux
> > mailing list style, so it is unnecessarily hard to read. In particular, it lacks
> > the line that shows what you're responding to.
> > It would look something like this:
> >
> > On Fri, Sep 23, 2022 at 11:21PM +0800, kernel test robot wrote:
>
> OK, thanks!
> I did a test just now, it seems to meet the format requirements.
> I sent emails via outlook, and I've tried to set the reply format,
> unfortunately, the time zone and date time are not resolved correctly.
Much better, thanks! It's much easier to read without all the
redundant headers.
Bjorn
next prev parent reply other threads:[~2022-09-27 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 13:24 [PATCH v1] PCI: Set no io resource for bridges that behind VMD controller Xiaochun Lee
2022-09-23 15:21 ` kernel test robot
2022-09-25 9:52 ` [External] " Xiaochun XC17 Li
2022-09-25 9:52 ` Xiaochun XC17 Li
2022-09-25 12:57 ` Bjorn Helgaas
2022-09-25 12:57 ` Bjorn Helgaas
2022-09-27 2:40 ` Xiaochun XC17 Li
2022-09-27 15:52 ` Bjorn Helgaas [this message]
2022-09-27 15:52 ` Bjorn Helgaas
2022-09-27 2:40 ` Xiaochun XC17 Li
2022-11-11 23:54 ` Bjorn Helgaas
2022-11-16 3:34 ` [External] " Xiaochun XC17 Li
2022-11-16 4:05 ` Bjorn Helgaas
2022-11-16 4:26 ` Xiaochun XC17 Li
2022-11-16 17:42 ` Bjorn Helgaas
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=20220927155203.GA1704003@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=jonathan.derrick@linux.dev \
--cc=kbuild-all@lists.01.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lixc17@lenovo.com \
--cc=lixiaochun.2888@163.com \
--cc=lkp@intel.com \
--cc=lpieralisi@kernel.org \
--cc=nirmal.patel@linux.intel.com \
--cc=robh@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.