From: Borislav Petkov <bp@alien8.de>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>,
intel-gfx@lists.freedesktop.org, x86@kernel.org,
linux-pci@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Intel-gfx] [PATCH V3] drm/i915/adl-n: Enable ADL-N platform
Date: Mon, 20 Dec 2021 12:33:26 +0100 [thread overview]
Message-ID: <YcBqBgnRVgyzUqUE@zn.tnic> (raw)
In-Reply-To: <20211219084921.lgd47srpzepspdpv@ldmartin-desk2>
On Sun, Dec 19, 2021 at 12:49:21AM -0800, Lucas De Marchi wrote:
> > I note not all such changes in git log have your acks recorded, though
> > most do. Do you want us to be more careful about Cc'ing you for acks on
> > PCI ID changes every time going forward?
>
> That's what Borislav asked in
> https://lore.kernel.org/all/20200520093025.GD1457@zn.tnic/
Right, I guess in the interest of not holding you guys up, if the patch
is only a trivial oneliner like below adding a GPU generation to the
list of quirks, you can only Cc x86@kernel.org so that we're aware and
proceed with it further without our ACK.
More involved stuff would need normal review, ofc.
Thx.
> > > diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
> > > index fd2d3ab38ebb..1ca3a56fdc2d 100644
> > > --- a/arch/x86/kernel/early-quirks.c
> > > +++ b/arch/x86/kernel/early-quirks.c
> > > @@ -554,6 +554,7 @@ static const struct pci_device_id intel_early_ids[] __initconst = {
> > > INTEL_RKL_IDS(&gen11_early_ops),
> > > INTEL_ADLS_IDS(&gen11_early_ops),
> > > INTEL_ADLP_IDS(&gen11_early_ops),
> > > + INTEL_ADLN_IDS(&gen11_early_ops),
> > > INTEL_RPLS_IDS(&gen11_early_ops),
> > > };
> > >
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-12-20 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211210051802.4063958-1-tejaskumarx.surendrakumar.upadhyay@intel.com>
2021-12-17 13:27 ` [Intel-gfx] [PATCH V3] drm/i915/adl-n: Enable ADL-N platform Jani Nikula
2021-12-18 9:31 ` Thomas Gleixner
2021-12-22 8:17 ` Jani Nikula
2021-12-19 8:49 ` Lucas De Marchi
2021-12-20 11:33 ` Borislav Petkov [this message]
2021-12-22 8:18 ` Jani Nikula
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=YcBqBgnRVgyzUqUE@zn.tnic \
--to=bp@alien8.de \
--cc=bhelgaas@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mingo@redhat.com \
--cc=tejaskumarx.surendrakumar.upadhyay@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox