From: R Sundar <prosunofficial@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: heikki.krogerus@linux.intel.com, dmitry.baryshkov@linaro.org,
neil.armstrong@linaro.org, christophe.jaillet@wanadoo.fr,
u.kleine-koenig@pengutronix.de, skhan@linuxfoundation.org,
javier.carrasco.cruz@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH v2] usb: typec: mux: replace of_node_put() with __free [linux-next]
Date: Sun, 5 May 2024 12:28:38 +0530 [thread overview]
Message-ID: <5c699755-0317-4485-af69-0a4256dce085@gmail.com> (raw)
In-Reply-To: <9574a4a1-a7b8-4f35-88b0-754c4396b02e@gmail.com>
On 05/05/24 10:50, R Sundar wrote:
> On 04/05/24 21:48, Greg KH wrote:
>> On Wed, Apr 10, 2024 at 11:28:04PM +0530, R SUNDAR wrote:
>>> Signed-off-by: R SUNDAR <prosunofficial@gmail.com>
>>
>> Please fix your name up for the next version.
>
> Hi,
>
> This version of patch is sent before comments provided for naming in
> patch v1.
>
> The name and nitpick was fixed after suggestion provided in patch v1.
>
> https://lore.kernel.org/all/2024041103-doornail-professor-7c1e@gregkh/
>
>
> Link for patch after fixing name and nitpick:
>
> https://lore.kernel.org/all/20240426164705.2717-1-prosunofficial@gmail.com/
>
>
>
> Thanks,
> Sundar
Little more explanation on previous mail:
Nitpick mentioned above , referring to is , suggestion to rewrite a
"nit in code" related to indentation in common path.
https://lore.kernel.org/all/2024041103-doornail-professor-7c1e@gregkh/
So along with fixing name , I fixed that indentations also as suggested.
https://lore.kernel.org/all/20240426164705.2717-1-prosunofficial@gmail.com/
Thanks,
Sundar
prev parent reply other threads:[~2024-05-05 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 17:58 [PATCH v2] usb: typec: mux: replace of_node_put() with __free [linux-next] R SUNDAR
2024-05-04 16:18 ` Greg KH
2024-05-05 5:20 ` R Sundar
2024-05-05 6:58 ` R Sundar [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=5c699755-0317-4485-af69-0a4256dce085@gmail.com \
--to=prosunofficial@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=skhan@linuxfoundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).