From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Florian Klink <flokli@flokli•de>
Cc: Jiri Kosina <jikos@kernel•org>,
Benjamin Tissoires <benjamin.tissoires@redhat•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
ValdikSS <iam@valdikss•org.ru>
Subject: Re: linux-next: Signed-off-by missing for commits in the hid tree
Date: Wed, 4 May 2022 07:55:41 +1000 [thread overview]
Message-ID: <20220504075541.30c8aba1@canb.auug.org.au> (raw)
In-Reply-To: <20220503212210.mqv3kxderfxesrue@tp.flokli.de>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
Hi Florian,
On Tue, 3 May 2022 23:22:10 +0200 Florian Klink <flokli@flokli•de> wrote:
>
> On 22-05-03 07:34:28, Stephen Rothwell wrote:
> >
> >Commits
> >
> > 5c9b8fae88bc ("HID: lenovo: Add note about different report numbers")
> > a0a5c2a69699 ("HID: lenovo: Sync Fn-lock state on button press for Compact and TrackPoint II keyboards")
> > 24401f291dcc ("HID: lenovo: Add support for ThinkPad TrackPoint Keyboard II")
> >
> >are missing a Signed-off-by from their author.
> >
>
> Yes, this is "intentional"/expected. See
> https://lore.kernel.org/all/20220121124116.cj6xtxvzw7rbkcs6@tp/.
>
> TL;DR: ValdikSS doesn't want to use a real name, and asked someone else
> to send this over (what I did).
>
> From my email linked there:
>
> > It seems the "real name" requirement only applies to the Signed-Off-By
> > (not Author) field, and sending a contribution provided by some other
> > person is covered by (c) in the DCO 1.1.
Thanks for clarifying.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-03 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:34 linux-next: Signed-off-by missing for commits in the hid tree Stephen Rothwell
2022-05-03 21:22 ` Florian Klink
2022-05-03 21:55 ` Stephen Rothwell [this message]
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=20220504075541.30c8aba1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=benjamin.tissoires@redhat$(echo .)com \
--cc=flokli@flokli$(echo .)de \
--cc=iam@valdikss$(echo .)org.ru \
--cc=jikos@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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