From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Gerhard Uttenthaler <uttenthaler@ems-wuensche.com>,
support@ems-wuensche.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-can@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v2 2/2] can: ems_pci: move ASIX AX99100 ids to pci_ids.h
Date: Wed, 26 Jul 2023 13:38:22 +0200 [thread overview]
Message-ID: <2023072657-unloved-magma-8cf2@gregkh> (raw)
In-Reply-To: <61bbb2e6-8c18-d2fc-ce1e-78d462ac1bba@linux.intel.com>
On Thu, Jul 20, 2023 at 10:54:01PM +0800, Jiaqing Zhao wrote:
> On 2023-07-20 18:40, Marc Kleine-Budde wrote:
> > On 20.07.2023 10:28:59, Jiaqing Zhao wrote:
> >> Move PCI Vendor and Device ID of ASIX AX99100 PCIe to Multi I/O
> >> Controller to pci_ids.h for its serial and parallel port driver
> >> support in subsequent patches.
> >
> > Sorry, I haven't noticed the change in "include/linux/pci_ids.h", that
> > the other patches depend on. How to coordinate among the subsystems?
> >
> > I don't mind taking the entire (v1) series with the Acks from the
> > tty/serial and parport maintainers, or give my Acked-by to upstream
> > via their trees.
>
> Add tty and parport maintainers to this thread.
>
> I'd like to ask other maintainers' opinion as I'm not sure which option
> is better and I had no similar experience before.
Either is fine with me, I can just take them all through my tty tree as
that's simplest for me :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-26 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 10:28 [PATCH v2 0/2] can: ems_pci: refine PCI IDs for ASIX AX99100 Jiaqing Zhao
2023-07-20 10:28 ` [PATCH v2 1/2] can: ems_pci: remove PCI_SUBVENDOR_ID_ASIX definition Jiaqing Zhao
2023-07-20 10:28 ` [PATCH v2 2/2] can: ems_pci: move ASIX AX99100 ids to pci_ids.h Jiaqing Zhao
2023-07-20 10:40 ` Marc Kleine-Budde
2023-07-20 14:54 ` Jiaqing Zhao
2023-07-26 11:38 ` Greg Kroah-Hartman [this message]
2023-07-26 11:47 ` Marc Kleine-Budde
2023-07-24 6:39 ` Jiaqing Zhao
2023-07-24 8:24 ` Marc Kleine-Budde
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=2023072657-unloved-magma-8cf2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=jiaqing.zhao@linux.intel.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=sudipm.mukherjee@gmail.com \
--cc=support@ems-wuensche.com \
--cc=uttenthaler@ems-wuensche.com \
--cc=wg@grandegger.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