From: sundar <prosunofficial@gmail.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: gregkh@linuxfoundation.org, neil.armstrong@linaro.org,
dmitry.baryshkov@linaro.org, u.kleine-koenig@pengutronix.de,
christophe.jaillet@wanadoo.fr, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
javier.carrasco.cruz@gmail.com
Subject: Re: [PATCH v4 linux-next] usb:typec:mux: remove indentation for common path
Date: Fri, 26 Apr 2024 20:17:29 +0530 [thread overview]
Message-ID: <559deef5-d437-4802-b3ec-78caab87355f@gmail.com> (raw)
In-Reply-To: <ZiukxoDxkLsIVG+Q@kuha.fi.intel.com>
On 26/04/24 18:27, Heikki Krogerus wrote:
> On Thu, Apr 25, 2024 at 08:15:04PM +0530, sundar wrote:
>> On 25/04/24 15:40, Heikki Krogerus wrote:
>>> On Wed, Apr 24, 2024 at 10:57:16PM +0530, sundar wrote:
>>>> Nitpick, Mostly common path will not be indented. so rewritten this
>>>> function to check device_node pointer is null and removed common path
>>>> indentation.
>>>>
>>>> Signed-off-by: sundar <prosunofficial@gmail.com>
>>>
>>> I don't think that is your full name, or is it?
>>>
>>> thanks,
>>>
>> Hi Heikki,
>>
>> Sundar is my full name.
>> Previously, I wrote my name in caps.after changing to small, conflict
>> arises.now I fixed it.
>
>
> You need to use your real, full name - what ever your name is in your
> passport. I find it a bit hard to believe you don't have a family (or
> given?) name.
>
> Your email returns couple of commits where you're name is "R SUNDAR".
> What does the "R" stand for?
>
> thanks,
>
Hi Heikki,
ok, so it will be R Sundar. I will change and send updated patch.
R is first letter of father's name.
sorry for inconvenience.
Regards,
Sundar.
prev parent reply other threads:[~2024-04-26 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 17:27 [PATCH v4 linux-next] usb:typec:mux: remove indentation for common path sundar
2024-04-25 10:10 ` Heikki Krogerus
2024-04-25 14:45 ` sundar
2024-04-26 12:57 ` Heikki Krogerus
2024-04-26 14:47 ` 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=559deef5-d437-4802-b3ec-78caab87355f@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.