On Thu, 15 Mar 2018, Jason Vas Dias wrote: > On 15/03/2018, Thomas Gleixner <[email protected]> wrote: > > On Thu, 15 Mar 2018, [email protected] wrote: > > > >> Resent to address reviewer comments. > > > > I was being patient so far and tried to guide you through the patch > > submission process, but unfortunately this turns out to be just waste of my > > time. > > > > You have not addressed any of the comments I made here: > > > > [1] > > https://lkml.kernel.org/r/[email protected] > > [2] > > https://lkml.kernel.org/r/[email protected] > > > > I'm really sorry about that - I did not see those mails , > and have searched for them in my inbox -
That's close to the 'my dog ate the homework' excuse. Of course they were sent to the list and to you personally as I used reply-all. From the mail server log: 2018-03-14 15:27:27 1ew7NH-00039q-Hv <= [email protected] [email protected] 2018-03-14 15:27:30 1ew7NH-00039q-Hv => [email protected] R=dnslookup T=remote_smtp H=gmail-smtp-in.l.google.com [2a00:1450:4013:c01::1a] X=TLS1.2:RSA_AES_128_CBC_SHA1:128 DN="C=US,ST=California,L=Mountain View,O=Google Inc,CN=mx.google.com" 2018-03-14 15:27:31 1ew7NH-00039q-Hv => [email protected] R=dnslookup T=remote_smtp H=vger.kernel.org [209.132.180.67] <SNIP other recipients on CC list> 2018-03-14 15:27:47 1ew7NH-00039q-Hv Completed If those messages would not have been delivered to [email protected] they would hardly be on the mailing list archive, right? And they both got delivered to your gmail account as well. > are you sure they were sent to '[email protected]' ? > That is the only list I am subscribed to . > I clicked on the links , but the 'To:' field is just > 'linux-kernel' . There is no 'To' field on that page. [prev in list] [next in list] [prev in thread] [next in thread] List: linux-kernel List != To. As any other sane archive it strips the To and Cc fields for obvious reasons. > If I had seen those messages before I re-submitted, > those issues would have been fixed. > > checkpatch.pl did not report them - > I ran it with all patches and it reported > no errors . patch 1/3: ERROR: Missing Signed-off-by: line(s) total: 1 errors, 0 warnings, 119 lines checked patch 2/3: ERROR: Missing Signed-off-by: line(s) total: 1 errors, 0 warnings, 71 lines checked patch 3/3: WARNING: externs should be avoided in .c files #24: FILE: arch/x86/entry/vdso/vclock_gettime.c:31: +extern unsigned int __vdso_tsc_calibration( WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #93: new file mode 100644 ERROR: Missing Signed-off-by: line(s) total: 1 errors, 2 warnings, 143 lines checked It reports an error for every single patch of your latest submission. > And I did send the test results in a previous mail - In private mail which I ignore if there is no real good reason. And just for the record. This private mail contains the following headers: In-Reply-To: <[email protected]> References: <[email protected]> <[email protected]> <[email protected]> From: Jason Vas Dias <[email protected]> Date: Wed, 14 Mar 2018 15:08:55 +0000 Message-ID: <calyzvkwb667x-adq4pe8p7_oc2-gdjwqcw4ch4naadmw9zo...@mail.gmail.com> Subject: Re: [PATCH v4.16-rc5 2/3] x86/vdso: on Intel, VDSO should handle CLOCK_MONOTONIC_RAW So now, if you take the message ID which is in the In-Reply-To: field and compare it to the message ID which I used for link [2]: In-Reply-To: <[email protected]> > > https://lkml.kernel.org/r/[email protected] you might notice that these are identical. So how did you end up replying to a mail which you never received? Nice try. I'm really fed up with this. Thanks, tglx
