From: Thomas Gleixner <tglx@linutronix.de>
To: OPENSOURCE Lukas Hannen
<lukas.hannen@opensource.tttech-industrial.com>,
John Stultz <john.stultz@linaro.org>,
"EMC: linux-kernel@vger.kernel.org"
<linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH] time: changed timespec64_to_ns to avoid underrun
Date: Sat, 11 Sep 2021 02:48:21 +0200 [thread overview]
Message-ID: <87fsucc4yy.ffs@tglx> (raw)
In-Reply-To: <AM0PR01MB54100B19D6ED5FDE764FA516EED69@AM0PR01MB5410.eurprd01.prod.exchangelabs.com>
Lukas,
On Fri, Sep 10 2021 at 13:50, OPENSOURCE Lukas Hannen wrote:
> This patch fixes a small oversight in timespec64_to_ns() that has resulted
...
why you are resending this patch?
1) The only change you did is adding a prefix to the subject line
which in fact disqualifies it from the RESEND tag because RESEND
means it's unmodified or just forward ported.
Changed patches even if the change is just in the subject line or the
changelog want a version number.
But what's worse:
2) You ignored any other review comment I gave here:
https://lore.kernel.org/r/87y2876pg0.ffs@tglx
IOW, you stopped reading at line 12 of my reply
3) Due to that you failed to notice that I said in that reply:
"I fixed it up for you this time."
4) Of course you also ignored the fact that I actually fixed the
identified issues and the fact that the fixed up patch is already
applied to my tree.
You got notfied about that:
https://lore.kernel.org/r/163111620295.25758.18154572095175068828.tip-bot2@tip-bot2
So what exactly are you trying to achieve by "resending" a patch which
still does not apply and still has a non-sensical subject line and
changelog?
> CONFIDENTIALITY: The contents of this e-mail are confidential and
> intended only for the above addressee(s). If you are not the intended
> recipient, or the person responsible for delivering it to the intended
> recipient, copying or delivering it to anyone else or using it in any
> unauthorized manner is prohibited and may be unlawful. If you receive
> this e-mail by mistake, please notify the sender and the systems
> administrator at straymail@tttech.com immediately.
Please get rid of this nonsensical disclaimer.
When posting to public mailing lists the boilerplate confidentiality
disclaimers are not only meaningless, they are absolutely wrong for
obvious reasons.
See https://people.kernel.org/tglx/notes-about-netiquette for further
information.
Thanks,
tglx
next prev parent reply other threads:[~2021-09-11 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 13:50 [RESEND PATCH] time: changed timespec64_to_ns to avoid underrun OPENSOURCE Lukas Hannen
2021-09-11 0:48 ` Thomas Gleixner [this message]
2021-09-13 6:49 ` OPENSOURCE Lukas Hannen
2021-09-13 8:23 ` Thomas Gleixner
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=87fsucc4yy.ffs@tglx \
--to=tglx@linutronix.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.hannen@opensource.tttech-industrial.com \
/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