From: Mario Limonciello <mario.limonciello@amd.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Thomas, Rijo-john" <Rijo-john.Thomas@amd.com>,
"David S. Miller" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Allen, John" <John.Allen@amd.com>
Subject: Re: [PATCH] crypto: ccp: Add support for TEE for PCI ID 0x14CA
Date: Wed, 12 Oct 2022 07:42:32 -0500 [thread overview]
Message-ID: <4e1bfb2e-cd9a-6b41-520e-dbf3746a2af8@amd.com> (raw)
In-Reply-To: <Y0aJhAmgF1mpxqNL@gondor.apana.org.au>
On 10/12/22 04:31, Herbert Xu wrote:
> On Fri, Oct 07, 2022 at 08:24:06PM +0000, Limonciello, Mario wrote:
>>
>> I noticed you sent out the 6.1 PR already. So I Just wanted to make sure this
>> didn't get overlooked as it's already got a T-b/A-b.
>
> Hi Mario:
>
> This didn't make the deadline for inclusion in my 6.1 PR. Is there
> any reason why it has to go in this merge window rather than the next?
>
> Thanks,
Some other maintainers take new IDs as fixes. Particularly when they're
good candidates for cc stable.
The main reason I wanted to see it sooner is so that it has more time to
percolate to the various downstream distros so that errors stemming from
the lack of this ID declaration aren't prevalent when using this SOC.
next prev parent reply other threads:[~2022-10-12 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 18:45 [PATCH] crypto: ccp: Add support for TEE for PCI ID 0x14CA Mario Limonciello
2022-09-28 21:05 ` Tom Lendacky
2022-10-07 20:24 ` Limonciello, Mario
2022-10-12 9:31 ` Herbert Xu
2022-10-12 12:42 ` Mario Limonciello [this message]
2022-10-13 1:55 ` Herbert Xu
2022-10-13 4:01 ` Limonciello, Mario
2022-10-21 11:34 ` Herbert Xu
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=4e1bfb2e-cd9a-6b41-520e-dbf3746a2af8@amd.com \
--to=mario.limonciello@amd.com \
--cc=John.Allen@amd.com \
--cc=Rijo-john.Thomas@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).