From: Jani Nikula <jani.nikula@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: x86@kernel.org, linux-pci@vger.kernel.org,
intel-gfx@lists.freedesktop.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: Wed, 22 Dec 2021 10:18:58 +0200 [thread overview]
Message-ID: <87r1a5yrv1.fsf@intel.com> (raw)
In-Reply-To: <YcBqBgnRVgyzUqUE@zn.tnic>
On Mon, 20 Dec 2021, Borislav Petkov <bp@alien8.de> wrote:
> 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.
Thanks, seems fair.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: 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: Wed, 22 Dec 2021 10:18:58 +0200 [thread overview]
Message-ID: <87r1a5yrv1.fsf@intel.com> (raw)
In-Reply-To: <YcBqBgnRVgyzUqUE@zn.tnic>
On Mon, 20 Dec 2021, Borislav Petkov <bp@alien8.de> wrote:
> 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.
Thanks, seems fair.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-12-22 8:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 5:18 [Intel-gfx] [PATCH V3] drm/i915/adl-n: Enable ADL-N platform Tejas Upadhyay
2021-12-10 10:48 ` Jani Nikula
2021-12-10 10:50 ` Surendrakumar Upadhyay, TejaskumarX
2021-12-16 11:49 ` Surendrakumar Upadhyay, TejaskumarX
2021-12-10 12:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/adl-n: Enable ADL-N platform (rev3) Patchwork
2021-12-10 12:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-10 13:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-11 8:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-12-16 11:57 ` [Intel-gfx] [PATCH V3] drm/i915/adl-n: Enable ADL-N platform Jani Nikula
2021-12-17 10:37 ` Srivatsa, Anusha
2021-12-17 13:27 ` Jani Nikula
2021-12-17 13:27 ` Jani Nikula
2021-12-18 9:31 ` Thomas Gleixner
2021-12-18 9:31 ` Thomas Gleixner
2021-12-22 8:17 ` Jani Nikula
2021-12-22 8:17 ` Jani Nikula
2021-12-19 8:49 ` Lucas De Marchi
2021-12-19 8:49 ` Lucas De Marchi
2021-12-20 11:33 ` Borislav Petkov
2021-12-20 11:33 ` Borislav Petkov
2021-12-22 8:18 ` Jani Nikula [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=87r1a5yrv1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-pci@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mingo@redhat.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 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.