From: Bjorn Helgaas <helgaas@kernel.org>
To: Slark Xiao <slark_xiao@163.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v2] PCI: Add vendor ID for Quectel and Cinterion
Date: Mon, 31 Oct 2022 09:58:49 -0500 [thread overview]
Message-ID: <20221031145849.GA1094273@bhelgaas> (raw)
In-Reply-To: <7a4b4099.3628.1842d4c7cc5.Coremail.slark_xiao@163.com>
On Mon, Oct 31, 2022 at 05:08:18PM +0800, Slark Xiao wrote:
> At 2022-10-29 00:06:21, "Bjorn Helgaas" <helgaas@kernel.org> wrote:
> >I think the best thing here would be two patches. One patch would add
> >PCI_VENDOR_ID_THALES to pci_ids.h and also add a use of it in the MHI
> >driver. The second patch would do the same for PCI_VENDOR_ID_QUECTEL.
> >
> >Then each one is logically self-contained.
>
> I must make sure these ids are applied, then I could commit the
> changes in MHI driver side. Otherwise it will cause build error.
>
> So I combine QUECTEL with THALES as a single patch. Shall I separate
> it from each other? 1 for PCI IDs, and another for MHI change. It
> would be better, I think.
Make two patches:
- A single patch that adds PCI_VENDOR_ID_THALES to pci_ids.h and
also adds a use of it in the MHI driver.
- A single patch that adds PCI_VENDOR_ID_QUECTEL to pci_ids.h and
also adds a use of it in the MHI driver.
That way there's no possibility of build error and no need to
coordinate patches.
Similar previous work:
https://git.kernel.org/linus/fae74feacd2d ("hisi_acc_qm: Move VF PCI device IDs to common header")
https://git.kernel.org/linus/d3826a95222c ("nfp: add support for NFP3800/NFP3803 PCIe devices")
https://git.kernel.org/linus/4fb0abfee424 ("x86/amd_nb: Add AMD Family 19h Models (10h-1Fh) and (A0h-AFh) PCI IDs")
prev parent reply other threads:[~2022-10-31 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 2:37 [PATCH v2] PCI: Add vendor ID for Quectel and Cinterion Slark Xiao
2022-10-28 3:51 ` Bagas Sanjaya
2022-10-28 3:57 ` Slark Xiao
2022-10-28 4:00 ` Bagas Sanjaya
2022-10-28 16:06 ` Bjorn Helgaas
2022-10-31 9:08 ` Slark Xiao
2022-10-31 14:58 ` 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=20221031145849.GA1094273@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=slark_xiao@163.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 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.