From: Bjorn Helgaas <helgaas@kernel.org>
To: "Patel, Nirmal" <nirmal.patel@linux.intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Linux PCI <linux-pci@vger.kernel.org>,
Jon Derrick <jonathan.derrick@linux.dev>
Subject: Re: [PATCH v2 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration
Date: Wed, 30 Mar 2022 13:20:48 -0500 [thread overview]
Message-ID: <20220330182048.GA1697467@bhelgaas> (raw)
In-Reply-To: <28c964fc-6392-c42a-fd85-7238da07ecfc@linux.intel.com>
On Wed, Mar 30, 2022 at 11:06:43AM -0700, Patel, Nirmal wrote:
> On 3/30/2022 10:54 AM, Bjorn Helgaas wrote:
> ...
> > This claims to be a v2, but I missed the v1, and the lore archives [1]
> > seem incomplete. Maybe the v1 (and maybe the cover letter?) were HTML
> > or got lost for some other reason?
> >
> > Bjorn
> >
> > [1] https://lore.kernel.org/all/?q=f%3Anirmal.patel
>
> Initially I created one patch [1] and I was advised to create two separate patches.
>
> [1] https://lore.kernel.org/all/358b0673-f90f-78ca-be66-51d5f76cc42b@linux.intel.com/
The point is that
https://lore.kernel.org/all/358b0673-f90f-78ca-be66-51d5f76cc42b@linux.intel.com/
is a reply to something that didn't make it into the archives.
It says:
In-Reply-To: <20220223075245.17744-1-nirmal.patel@linux.intel.com>
but 20220223075245.17744-1-nirmal.patel@linux.intel.com is unknown to
lore.
You can't fix this now; I'm just pointing it out in case there's some
problem with the way you're sending patches.
Bjorn
next prev parent reply other threads:[~2022-03-30 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220316155103.8415-1-nirmal.patel@intel.com>
2022-03-29 22:47 ` [PATCH v2 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration Patel, Nirmal
2022-03-29 23:27 ` Dan Williams
2022-03-30 15:54 ` Patel, Nirmal
2022-03-30 17:54 ` Bjorn Helgaas
2022-03-30 18:06 ` Patel, Nirmal
2022-03-30 18:20 ` Bjorn Helgaas [this message]
[not found] ` <20220316155103.8415-2-nirmal.patel@intel.com>
2022-03-29 22:48 ` [PATCH v2 2/2] Allow VMD to disable MSIX remapping with interrupt remapping enabled Patel, Nirmal
2022-03-30 17:49 ` Bjorn Helgaas
2022-03-30 18:07 ` Patel, Nirmal
2022-05-11 9:57 [PATCH v2 0/2] PCI: vmd: IRQ domain assignment to sub devices Nirmal Patel
2022-05-11 9:57 ` [PATCH v2 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration Nirmal Patel
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=20220330182048.GA1697467@bhelgaas \
--to=helgaas@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=jonathan.derrick@linux.dev \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nirmal.patel@linux.intel.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).