From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Lutomirski <luto@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] x86/vdso: Give the [ph]vclock_page declarations real types
Date: Mon, 24 Jun 2019 00:19:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1906240019130.32342@nanos.tec.linutronix.de> (raw)
In-Reply-To: <49C4F6B3-D419-4035-B49D-1586912C670C@amacapital.net>
On Sun, 23 Jun 2019, Andy Lutomirski wrote:
>
> > On Jun 23, 2019, at 6:10 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> >> On Sun, 23 Jun 2019, Linus Torvalds wrote:
> >>
> >> Andy added comments and changed the patch in other ways too, so I think
> >> it's fine to have him as author, and my sign-off is just for the original
> >> smaller patch.
> >
> > Well, that will earn me a nastigram from the next checkers as it's not
> > compliant to our SOB rules ....
> >
>
> Feel free to add:
>
> Originally-by: Linus ...
>
> I had assumed the textual description was enough.
Ha, completely forgot about Co-developed-by. That does the trick nicely.
next prev parent reply other threads:[~2019-06-24 3:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 22:08 [PATCH] x86/vdso: Give the [ph]vclock_page declarations real types Andy Lutomirski
2019-06-23 12:42 ` Thomas Gleixner
[not found] ` <CAHk-=whywzng7FLV9X67RPmHNnygK+7VJV+zh4njT6BA+h9tCw@mail.gmail.com>
2019-06-23 13:10 ` Thomas Gleixner
2019-06-23 16:03 ` Andy Lutomirski
2019-06-23 22:19 ` Thomas Gleixner [this message]
2019-06-23 23:57 ` [tip:timers/vdso] " tip-bot for Andy Lutomirski
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=alpine.DEB.2.21.1906240019130.32342@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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).