From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: Maxime Ripard <maxime@cerno.tech>, "B.R. Oake" <broake@mailfence.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com, Rob Herring <robh+dt@kernel.org>,
Chen-Yu Tsai <wens@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: sun8i: h3: orangepi-plus: Fix Ethernet PHY mode
Date: Sat, 13 Feb 2021 09:51:17 +0100 [thread overview]
Message-ID: <6612268.HtAl026vyE@jernej-laptop> (raw)
In-Reply-To: <1719200956.433094.1613199092092@ichabod.co-bxl>
Hi!
Let me first explain that it was oversight on my side not noticing initials in
your SoB tag. But since the issue was raised by Maxime, I didn't follow up.
Dne sobota, 13. februar 2021 ob 07:51:32 CET je B.R. Oake napisal(a):
> On Wed Feb 10 at 16:01:18 CET 2021, Maxime Ripard wrote:
> > Unfortunately we can't take this patch as is, this needs to be your real
> > name, see:
> > https://www.kernel.org/doc/html/latest/process/submitting-patches.html#de
> > veloper-s-certificate-of-origin-1-1
> Dear Maxime,
>
> Thank you very much for considering my contribution and for all your
> work on supporting sunxi-based hardware; I appreciate it.
>
> Thank you for referring me to the Developer's Certificate of Origin, but
> I had already read it before submitting (I had to do so in order to know
> what I was saying by "Signed-off-by:") and I do certify what it says.
>
> Looking through recent entries in the commit log of the mainline kernel,
> I see several patches from authors such as:
>
> H.J. Lu <hjl.tools@gmail.com>
> B K Karthik <karthik.bk2000@live.com>
> JC Kuo <jckuo@nvidia.com>
> EJ Hsu <ejh@nvidia.com>
> LH Lin <lh.lin@mediatek.com>
> KP Singh <kpsingh@kernel.org>
> Karthik B S <karthik.b.s@intel.com>
> Shreyas NC <shreyas.nc@intel.com>
> Vandana BN <bnvandana@gmail.com>
>
> so I believe names of this form are in fact acceptable, even if the
> style might seem a little old-fashioned to some.
Speaking generally, not only for this case, prior art arguments rarely hold,
because:
- it might be oversight,
- it might be a bad practice, which should not be followed in new
contributions,
- different maintainers have different point of view on same thing,
- maintainer wants to adapt new practice or steer subsystem in new direction
>
> I would like to add that I have met many people with names such as C.J.,
> A A, TC, MG, etc. That is what everybody calls them and it would be
> natural for them to sign themselves that way. Some of them might want to
> contribute to Linux some day, and I think it would be a great shame and
> a loss to all of us if they were discouraged from doing so by reading
> our conversation in the archives and concluding that any contribution
> from them, however small, would be summarily refused simply because of
> their name. Please could you ensure that does not happen?
The link you posted says following:
"using your real name (sorry, no pseudonyms or anonymous contributions.)"
I believe that real name means no initials, no matter what people are
accustomed to. From my point of view, CJ is pseudonym derived from real name.
This is not the first time that fix of SoB tag was requested, you can find such
requests in ML archives.
Best regards,
Jernej
>
> Thank you again for your consideration.
>
> Yours sincerely,
> B.R. Oake.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-13 8:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 11:24 [PATCH] ARM: dts: sun8i: h3: orangepi-plus: Fix Ethernet PHY mode B.R. Oake
2021-02-08 11:27 ` Jernej Škrabec
2021-02-10 15:01 ` Maxime Ripard
2021-02-13 6:51 ` B.R. Oake
2021-02-13 8:51 ` Jernej Škrabec [this message]
2021-05-16 16:58 ` Salvatore Bonaccorso
2021-05-16 20:18 ` Vagrant Cascadian
2021-05-18 15:06 ` Maxime Ripard
2021-05-18 20:25 ` Salvatore Bonaccorso
2021-05-18 20:43 ` Salvatore Bonaccorso
2021-05-20 18:24 ` Vagrant Cascadian
2021-05-20 18:50 ` Salvatore Bonaccorso
2021-05-24 11:55 ` Maxime Ripard
2021-05-24 12:26 ` Salvatore Bonaccorso
2021-06-04 4:19 ` B.R. Oake
2021-06-04 6:49 ` [linux-sunxi] " Julian Calaby
2021-07-05 0:18 ` B.R. Oake
2021-07-05 0:48 ` Julian Calaby
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=6612268.HtAl026vyE@jernej-laptop \
--to=jernej.skrabec@siol.net \
--cc=broake@mailfence.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime@cerno.tech \
--cc=robh+dt@kernel.org \
--cc=wens@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).