public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 25 Sep 2022 07:57:04 -0500	[thread overview]
Message-ID: <20220925125704.GA1529068@bhelgaas> (raw)
In-Reply-To: <SEYPR03MB68772E818ECCE020FEF785DBBC539@SEYPR03MB6877.apcprd03.prod.outlook.com>

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
> > 
> > Hi Xiaochun,
> > 
> > Thank you for the patch! Yet something to improve:
> > 
> > [auto build test ERROR on helgaas-pci/next] [also build test ERROR on
> > linus/master v6.0-rc6 next-20220923] [If your patch is applied to the wrong
> > git tree, kindly drop us a note.
> Hi, thanks for your reply, this patch is only expected to be applied
> on x86 or x64, actually function "is_vmd()" is just defined in
> arch/x86/include/asm/pci.h, do we need to support it on arch um?

Yes, all possible Kconfig configurations must build cleanly.  You
may have to add additional ifdef tests or an is_vmd() stub.

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:

Here's a sample:
https://lore.kernel.org/r/YyGghUdcrOdrR0ep@smile.fi.intel.com

More background:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  reply	other threads:[~2022-09-25 13:00 UTC|newest]

Thread overview: 11+ 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 12:57     ` Bjorn Helgaas [this message]
2022-09-27  2:40       ` Xiaochun XC17 Li
2022-09-27 15:52         ` Bjorn Helgaas
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=20220925125704.GA1529068@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox