From: Sudeep Holla <sudeep.holla@arm.com>
To: Adam Young <admiyo@amperemail.onmicrosoft.com>
Cc: Adam Young <admiyo@os.amperecomputing.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Huisong Li <lihuisong@huawei.com>
Subject: Re: [PATCH v30 1/3] mailbox: pcc: Type3 Buffer handles ACK IRQ
Date: Fri, 17 Oct 2025 18:42:09 +0100 [thread overview]
Message-ID: <aPJ_8XJyse50Tgfx@bogus> (raw)
In-Reply-To: <99aa7b2a-e772-4a93-a724-708e8e0a21ed@amperemail.onmicrosoft.com>
On Fri, Oct 17, 2025 at 12:08:07PM -0400, Adam Young wrote:
> This is obsoleted/duplicated by Sudeep's patch. I am going to rebase on his
> patch series.
>
Thanks for looking at them. Sorry we just cross posted each other last night.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-10-17 17:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 21:02 [PATCH v30 0/3] MCTP Over PCC Transport Adam Young
2025-10-16 21:02 ` [PATCH v30 1/3] mailbox: pcc: Type3 Buffer handles ACK IRQ Adam Young
2025-10-17 16:08 ` Adam Young
2025-10-17 17:42 ` Sudeep Holla [this message]
2025-10-17 18:04 ` Adam Young
2025-10-16 21:02 ` [PATCH v30 2/3] mailbox: pcc: functions for reading and writing PCC extended data Adam Young
2025-10-17 10:12 ` [External] : " ALOK TIWARI
2025-10-20 12:52 ` Sudeep Holla
2025-10-20 17:22 ` Adam Young
2025-10-21 14:02 ` Sudeep Holla
2025-10-21 17:20 ` Adam Young
2025-10-24 13:50 ` Sudeep Holla
2025-12-18 19:31 ` Adam Young
2025-10-16 21:02 ` [PATCH v30 3/3] mctp pcc: Implement MCTP over PCC Transport Adam Young
2025-10-17 3:01 ` Jeremy Kerr
2025-10-21 0:54 ` Adam Young
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=aPJ_8XJyse50Tgfx@bogus \
--to=sudeep.holla@arm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=admiyo@amperemail.onmicrosoft.com \
--cc=admiyo@os.amperecomputing.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jassisinghbrar@gmail.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).