lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 9 Dec 2020 15:21:11 +0200
From:   Vladimir Oltean <olteanv@...il.com>
To:     Aswin C <realc@...tonmail.com>
Cc:     Aswin C <aswinraman2013@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>, Andrew Lunn <andrew@...n.ch>,
        Florian Fainelli <f.fainelli@...il.com>,
        Vivien Didelot <vivien.didelot@...il.com>
Subject: Re: [PATCH] net: dsa: sja1105: Remove an unprofessional word from
 the code comments

Hi Aswin,

On Wed, Dec 09, 2020 at 11:54:20AM +0000, Aswin C wrote:
> Hello. Thank you very much for the reply.
>
> Firstly, yes, it's my first contribution and apologies for making some
> mistakes and I'd like to thank you for being kind and pointing it out.

No problem. Nobody is born educated, it is through mistakes that we learn.
There is also a convention for replying to email, I might add. It is to
trim down the quoted portion only to what you are replying to, and to
reply below it (and not above, aka top-posting), and to use plain text
and not HTML. This is how your email looks like in plain text. It
doesn't look pleasant to read:
https://lore.kernel.org/lkml/-gMuTlvCAcfhIMqI1V4ylxBXKdWffUwznP_0cODJaam4l3hyfEFTLkZUZMLQV23BCeO8S6vTh1OfN0yOi7M5PhfX0rOX8SkL9JknVM2nKOA=@protonmail.com/
Try to configure your email client to use plain text.

> I came to know about this driver in a casual discussion among my peers
> when one of them pointed out the presence of this particular word on
> the driver.

Who are your peers and why do they care about the Linux driver for an
automotive Ethernet switch?

> I just thought that I'd try to help and get rid of that, if possible.
> Nothing more.

So you do consider that getting rid of it is helpful. Please elaborate.

> As you mentioned, I ran my eyes over drivers/net/dsa/sja1105/sja1105_tas.c
> and the other files. Other than a very minor spelling error, I didn't
> come across wording conventions like the one we are discussing about.

Read more.

> And yes, as you mentioned, "poorly organized" sounds perfect, too.

Well, even though it may sound better to you, I am still not sure I
agree with the change. To reiterate, "professional" was not a goal of
this driver. There are other professional drivers for this hardware.
It is all for fun.

I find that suppressing negative emotions, anger, frustration, is not
helpful, as it tends to only amplify them over time. Instead, learning
to disguise aggressivity, controlling it, making it more subtle and
never directing it towards people can be good ways to let it out.
If I wasn't subtle enough or it really bothered you, I'm open to improve
and do better next time, but you'll have to convince me.

And this is not only about me. In general I believe that you will not
receive a positive reaction from people when you point out to them that
they should watch out for their language in circumstances that really do
not make any difference to you. The linux mailing lists are an amazing
place to learn from people. But engineers do not have good social
skills. You need to make concessions to others' personalities before you
could focus on the good part and learn from them. I think it would be a
shame to start your contributions to the Linux kernel in this way, by
making the language less vulgar. You sure won't be making any friends.
There are plenty of other areas you could concentrate on.

> I believe that not signing off and not sending it to all maintainers
> is all, in the things I did wrong. So, I hope I can fix them and send
> the patch as a reply to this thread.

Do not send follow-up patches in reply to existing threads. They get
lost by maintainers.
Instead, use git send-email --cover-letter="PATCH v2 net-next" and be
sure to send it to the maintainers and the networking mailing list.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ