From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D398AC001DF for ; Tue, 11 Jul 2023 15:43:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230446AbjGKPnO (ORCPT ); Tue, 11 Jul 2023 11:43:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56318 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233286AbjGKPm7 (ORCPT ); Tue, 11 Jul 2023 11:42:59 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7AB721BCC; Tue, 11 Jul 2023 08:42:15 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 3AC7F2275C; Tue, 11 Jul 2023 15:42:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1689090134; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rQYkKfGFGC5pVN3aJkpbpkhHDlSbsj+GelqxV7zZTRk=; b=UfQ4urB4+8BgTndkCc7fCiD3ME3yHDkc4GP5nB/e9EIsE/TMJJFKSb8Uo+WvN9EmPVizRO 1zbuOk0jlFMYDrrqOoJ0UJd4woZwQ8jdxnOUDtwwSXYvkzL/FhicmT6qrzsRWIN8eYjy2L pCOcupFyxCMKJEu/HUUsyjdzYRa1gKc= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1689090134; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rQYkKfGFGC5pVN3aJkpbpkhHDlSbsj+GelqxV7zZTRk=; b=TYUBrLVvAW/nJukV/0wT380gWBhvaXjoaLokOXLrdH4Dys9++VALmNxWyyZx+Q4jrleDfB PTQsaFoVjhbLmMDQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id EAE081390F; Tue, 11 Jul 2023 15:42:13 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id FWnaN1V4rWRKIgAAMHmgww (envelope-from ); Tue, 11 Jul 2023 15:42:13 +0000 Date: Tue, 11 Jul 2023 17:42:13 +0200 Message-ID: <87jzv6h2ui.wl-tiwai@suse.de> From: Takashi Iwai To: Mark Brown Cc: Pierre-Louis Bossart , Amadeusz =?ISO-8859-2?Q?S=B3awi=F1ski?= , Bjorn Helgaas , Takashi Iwai , alsa-devel@alsa-project.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Cezary Rojewski , Kai Vehmanen , Andy Shevchenko , Hans de Goede Subject: Re: [PATCH 00/13] PCI: Define Intel PCI IDs and use them in drivers In-Reply-To: <46d612f4-24a4-4493-aa9f-0ace5225a38b@sirena.org.uk> References: <20230711125726.3509391-1-amadeuszx.slawinski@linux.intel.com> <46d612f4-24a4-4493-aa9f-0ace5225a38b@sirena.org.uk> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Tue, 11 Jul 2023 17:36:20 +0200, Mark Brown wrote: > > On Tue, Jul 11, 2023 at 05:24:07PM +0200, Pierre-Louis Bossart wrote: > > On 7/11/23 14:57, Amadeusz Sławiński wrote: > > > > Simplify things, by adding PCI IDs to global header and make use of them > > > in drivers. This allows for removal of comments by having IDs themselves > > > being self explanatory. Additionally it allows for removal of existing > > > inconsistencies by having one source of truth. > > > I'd like to hear from Takashi and Mark on how this would work, we have > > to provide new PCI IDs for both trees using a common 'pci_ids.h' file. > > We can probably just agree on a tree to apply things and work from > there. Yes, simply apply on top of 6.5-rc1 or such a stable point and tag it. Then other trees can merging it. I can do it if both Bjorn and Mark agree (after all patches get reviewed and no objection comes up). Takashi