From: Jakub Kicinski <kuba@kernel•org>
To: Siddharth Vadapalli <s-vadapalli@ti•com>
Cc: <davem@davemloft•net>, <edumazet@google•com>,
<linux@armlinux•org.uk>, <pabeni@redhat•com>, <rogerq@kernel•org>,
<leon@kernel•org>, <leonro@nvidia•com>,
<anthony.l.nguyen@intel•com>, <netdev@vger•kernel.org>,
<linux-kernel@vger•kernel.org>,
<linux-arm-kernel@lists•infradead.org>, <vigneshr@ti•com>,
<srk@ti•com>
Subject: Re: [PATCH net-next v4 2/2] net: ethernet: ti: am65-cpsw/cpts: Fix CPTS release action
Date: Thu, 19 Jan 2023 21:48:00 -0800 [thread overview]
Message-ID: <20230119214800.63b8c63a@kernel.org> (raw)
In-Reply-To: <20230120044201.357950-1-s-vadapalli@ti.com>
On Fri, 20 Jan 2023 10:12:01 +0530 Siddharth Vadapalli wrote:
> Changes from v3:
> 1. Rebase patch on net-next commit: cff9b79e9ad5
> 2. Collect Reviewed-by tags from Leon Romanovsky, Tony Nguyen and
> Roger Quadros.
You need to repost the entire series, and please don't --in-reply-to,
just CC the people who commented.
next prev parent reply other threads:[~2023-01-20 5:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 9:54 [PATCH net-next v3 0/2] Fix CPTS release action in am65-cpts driver Siddharth Vadapalli
2023-01-18 9:54 ` [PATCH net-next v3 1/2] net: ethernet: ti: am65-cpsw: Delete unreachable error handling code Siddharth Vadapalli
2023-01-18 11:30 ` Leon Romanovsky
2023-01-18 9:54 ` [PATCH net-next v3 2/2] net: ethernet: ti: am65-cpsw/cpts: Fix CPTS release action Siddharth Vadapalli
2023-01-18 11:29 ` Leon Romanovsky
2023-01-19 13:06 ` Paolo Abeni
2023-01-20 4:42 ` [PATCH net-next v4 " Siddharth Vadapalli
2023-01-20 5:48 ` Jakub Kicinski [this message]
2023-01-20 5:52 ` Siddharth Vadapalli
2023-01-18 21:24 ` [PATCH net-next v3 0/2] Fix CPTS release action in am65-cpts driver Tony Nguyen
2023-01-19 10:27 ` Roger Quadros
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=20230119214800.63b8c63a@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=leonro@nvidia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=rogerq@kernel$(echo .)org \
--cc=s-vadapalli@ti$(echo .)com \
--cc=srk@ti$(echo .)com \
--cc=vigneshr@ti$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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