From: Kousik Sanagavarapu <five231003@gmail.com>
To: Nishanth Menon <nm@ti.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] Do device node auto cleanup in drivers/soc/ti/
Date: Thu, 18 Jul 2024 19:42:07 +0530 [thread overview]
Message-ID: <ZpkitzRCeCz9RQtn@five231003> (raw)
In-Reply-To: <20240718112134.txuimtlg62375jaw@musky>
On Thu, Jul 18, 2024 at 06:21:34AM -0500, Nishanth Menon wrote:
> On 03:04-20240718, Kousik Sanagavarapu wrote:
>
> [...]
>
> > Ping
>
> Umm... ping for what? for whom and why? In addition to reviews, I will
> need someone to do tested-by as well - pruss/am33xx folks..? Further,
> fyi, 6.12 collection cycle starts with 6.11 rc1 and I close mine around
> rc4.
Sorry for not being more specific. Since the last version was reviewed
by Jonathan, I was wondering if he could review this round too.
And yes, it would be great if someone could test these patches as I don't
have access to the hardware - so RFT.
Also thanks for the heads up on the cycle, I didn't know.
Thanks
prev parent reply other threads:[~2024-07-18 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 5:14 [PATCH v3 0/4] Do device node auto cleanup in drivers/soc/ti/ Kousik Sanagavarapu
2024-07-07 5:14 ` [PATCH v3 1/4] soc: ti: pruss: factor out memories setup Kousik Sanagavarapu
2024-08-24 18:49 ` Nishanth Menon
2024-08-25 6:38 ` Kousik Sanagavarapu
2024-07-07 5:14 ` [PATCH v3 2/4] soc: ti: pruss: do device_node auto cleanup Kousik Sanagavarapu
2024-07-07 5:14 ` [PATCH v3 3/4] soc: ti: knav_qmss_queue: " Kousik Sanagavarapu
2024-07-07 5:14 ` [PATCH v3 4/4] soc: ti: pm33xx: " Kousik Sanagavarapu
2024-07-17 21:34 ` [PATCH v3 0/4] Do device node auto cleanup in drivers/soc/ti/ Kousik Sanagavarapu
2024-07-18 11:21 ` Nishanth Menon
2024-07-18 14:12 ` Kousik Sanagavarapu [this message]
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=ZpkitzRCeCz9RQtn@five231003 \
--to=five231003@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nm@ti.com \
--cc=skhan@linuxfoundation.org \
--cc=ssantosh@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).