From: Bjorn Helgaas <helgaas@kernel.org>
To: Xiaochun XC17 Li <lixc17@lenovo.com>
Cc: Xiaochun Lee <lixiaochun.2888@163.com>,
"nirmal.patel@linux.intel.com" <nirmal.patel@linux.intel.com>,
"jonathan.derrick@linux.dev" <jonathan.derrick@linux.dev>,
"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: Wed, 16 Nov 2022 11:42:05 -0600 [thread overview]
Message-ID: <20221116174205.GA1122329@bhelgaas> (raw)
In-Reply-To: <SEYPR03MB68773929A3008A3F5C7E0898BC079@SEYPR03MB6877.apcprd03.prod.outlook.com>
On Wed, Nov 16, 2022 at 04:26:02AM +0000, Xiaochun XC17 Li wrote:
> On Wed, Nov 16, 2022 at 12:10 PM +0800, "Bjorn Helgaas" <helgaas@kernel.org> wrote:
> > 2) Some of your previous patches didn't make it to the mailing list, so we
> > couldn't really do anything with them.
> >
> > Bjorn
>
> Actually, the V2 patch didn't following the mailing of V1 patch, I
> sent it out separately like the first time for V1 patch, I don't
> know if there is a mistake in the way I sent the V2 patch. I was
> wondering if I was going to send out V2 patches based on the mailing
> list of V1 patch, if it is yes, I must study how to summit the V2
> patch, so would you please correct me?
I was mistaken, the V2 patch *was* on the mailing list:
https://lore.kernel.org/r/1664288166-7432-1-git-send-email-lixiaochun.2888@163.com
I guess I didn't find it because I was searching for the email address
"lixc17@lenovo.com", and v2 was posted by "lixiaochun.2888@163.com".
Sorry, my mistake! It looks like the sending of v2 was just fine.
Bjorn
prev parent reply other threads:[~2022-11-16 17:42 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 12:57 ` Bjorn Helgaas
2022-09-25 12:57 ` Bjorn Helgaas
2022-09-27 2:40 ` Xiaochun XC17 Li
2022-09-27 2:40 ` Xiaochun XC17 Li
2022-09-27 15:52 ` Bjorn Helgaas
2022-09-27 15:52 ` Bjorn Helgaas
2022-09-25 9:52 ` 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 [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=20221116174205.GA1122329@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=jonathan.derrick@linux.dev \
--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=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.