From: Thomas Zimmermann <tzimmermann@suse.de>
To: Damien Le Moal <dlemoal@kernel.org>, Bjorn Helgaas <helgaas@kernel.org>
Cc: "open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRM DRIVER FOR AST SERVER GRAPHICS CHIPS"
<dri-devel@lists.freedesktop.org>,
linux-ide@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Dave Airlie <airlied@redhat.com>,
Patrick McLean <chutzpah@gentoo.org>
Subject: Re: [PATCH] PCI: Add ASPEED vendor ID
Date: Fri, 21 Apr 2023 08:49:43 +0200 [thread overview]
Message-ID: <b28f6831-3be1-305e-72a5-c4df4e5f6eba@suse.de> (raw)
In-Reply-To: <6b7c1f22-2d97-bda9-affd-2e3a7a1d42ed@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 2626 bytes --]
Hi
Am 21.04.23 um 00:04 schrieb Damien Le Moal:
> On 4/21/23 04:10, Bjorn Helgaas wrote:
>> [+cc Damien, linux-ide]
>>
>> On Thu, Apr 20, 2023 at 09:08:48AM +0200, Thomas Zimmermann wrote:
>>> Am 19.04.23 um 20:37 schrieb Bjorn Helgaas:
>>>> On Wed, Apr 19, 2023 at 09:00:15AM +0200, Thomas Zimmermann wrote:
>>>>> Am 19.04.23 um 00:57 schrieb Patrick McLean:
>>>>>> Currently the ASPEED PCI vendor ID is defined in
>>>>>> drivers/gpu/drm/ast/ast_drv.c, move that to include/linux/pci_ids.h
>>>>>> with all the rest of the PCI vendor ID definitions. Rename the definition
>>>>>> to follow the format that the other definitions follow.
>>>>>
>>>>> Thanks a lot. Can you please also move and rename the PCI device ids? [1]
>>>>
>>>> Generally we move things to pci_ids.h only when they are shared
>>>> between multiple drivers. This is mostly to make backports easier.
>>>>
>>>> PCI_VENDOR_ID_ASPEED is (or will be) used in both ast_drv.c and
>>>> libata-core.c, so it qualifies.
>>>>
>>>> It doesn't look like PCI_CHIP_AST2000 and PCI_CHIP_AST2100 would
>>>> qualify since they're only used in ast_drv.c and ast_main.c, which are
>>>> part of the same driver.
>>>
>>> Ok, I see. Can I take the patch into DRM trees?
>>
>> The first time around I got two patches [2]. This time I only got
>> this patch, but IIUC there are still two patches in play here:
>>
>> - This one, which moves PCI_VENDOR_ID_ASPEED to pci_ids.h, and
>> - The libata-core one that adds a use in ata_dev_config_ncq()
>>
>> Those should go together via the same tree. I supplied my ack to
>> indicate that I'm not going to merge anything myself, and I expect
>> whoever merges the libata patch to also merge this one.
>>
>> If for some reason the libata-core patch doesn't happen, then this
>> patch shouldn't happen either, because there would no longer be any
>> sharing between drivers that would justify a pci_ids.h addition.
>
> I can take both patches through the libata tree but there were comments on the
> second patch for libata and I have not seen these addressed yet (I did not get a
> v2). And in the meantime, it seems that the PCI ID patch was reworked as a
> single patch... Not sure what's happening here.
I don't think I've even seen the libata patch. Please take both patches
through your tree when they are ready.
Best regards
Thomas
>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-04-21 6:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 22:57 [PATCH] PCI: Add ASPEED vendor ID Patrick McLean
2023-04-19 7:00 ` Thomas Zimmermann
2023-04-19 18:37 ` Bjorn Helgaas
2023-04-19 18:37 ` Bjorn Helgaas
2023-04-20 7:08 ` Thomas Zimmermann
2023-04-20 19:10 ` Bjorn Helgaas
2023-04-20 19:10 ` Bjorn Helgaas
2023-04-20 22:04 ` Damien Le Moal
2023-04-20 22:04 ` Damien Le Moal
2023-04-21 6:49 ` Thomas Zimmermann [this message]
2023-04-19 18:39 ` Bjorn Helgaas
2023-04-19 18:39 ` Bjorn Helgaas
2023-04-20 7:09 ` Thomas Zimmermann
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=b28f6831-3be1-305e-72a5-c4df4e5f6eba@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=bhelgaas@google.com \
--cc=chutzpah@gentoo.org \
--cc=dlemoal@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=helgaas@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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.