From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Wolfram Sang <wsa@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
linux-crypto@vger.kernel.org, linux-i2c@vger.kernel.org,
Held Felix <Felix.Held@amd.com>,
linux-kernel@vger.kernel.org,
Mark Hasemeyer <markhas@chromium.org>,
Grzegorz Bernacki <gjb@semihalf.com>
Subject: Re: [PATCH v8 0/6] Use CCP driver to handle PSP I2C arbitration
Date: Wed, 12 Apr 2023 11:28:44 -0500 [thread overview]
Message-ID: <e53a03cf-71ce-1864-5700-b48e8beb17a6@amd.com> (raw)
In-Reply-To: <ZC+1ufdj8WYixQsM@sai>
On 4/7/2023 01:18, Wolfram Sang wrote:
>
>>> How should this go upstream, i.e. are there dependencies? Shall I pick
>>> the I2C patches or is it better if all goes via the crypto tree?
>>>
>> IMO it's better to go through the crypto tree. There are dependencies
>> in the crypto part from the earlier series that was merged.
>
> Ok, fine with me. I acked the I2C patches. Thanks for the heads up.
>
Herbert,
Would you mind to queue these up for -next? I do have some other
separate work I will be submitting that is going to layer on top of
them, so I'd like to base it off your branch with these landed.
next prev parent reply other threads:[~2023-04-12 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 18:32 [PATCH v8 0/6] Use CCP driver to handle PSP I2C arbitration Mario Limonciello
2023-04-03 18:32 ` [PATCH v8 1/6] crypto: ccp: Drop extra doorbell checks Mario Limonciello
2023-04-03 18:32 ` [PATCH v8 2/6] crypto: ccp: Bump up doorbell debug message to error Mario Limonciello
2023-04-03 18:32 ` [PATCH v8 3/6] crypto: ccp: Return doorbell status code as an argument Mario Limonciello
2023-04-03 18:32 ` [PATCH v8 4/6] crypto: ccp: Use lower 8 bytes to communicate with doorbell command register Mario Limonciello
2023-04-06 6:42 ` [PATCH v8 0/6] Use CCP driver to handle PSP I2C arbitration Wolfram Sang
2023-04-06 11:58 ` Mario Limonciello
2023-04-07 6:18 ` Wolfram Sang
2023-04-12 16:28 ` Limonciello, Mario [this message]
2023-04-14 11:05 ` 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=e53a03cf-71ce-1864-5700-b48e8beb17a6@amd.com \
--to=mario.limonciello@amd.com \
--cc=Felix.Held@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gjb@semihalf.com \
--cc=herbert@gondor.apana.org.au \
--cc=jsd@semihalf.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markhas@chromium.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@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