From: Florian Klink <flokli@flokli.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Tue, 3 May 2022 23:22:10 +0200 [thread overview]
Message-ID: <20220503212210.mqv3kxderfxesrue@tp.flokli.de> (raw)
In-Reply-To: <20220503073428.219a0ed8@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Hey Stephen,
On 22-05-03 07:34:28, Stephen Rothwell wrote:
>Hi all,
>
>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.
Regards,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-03 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:34 Stephen Rothwell
2022-05-03 21:22 ` Florian Klink [this message]
2022-05-03 21:55 ` Stephen Rothwell
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=20220503212210.mqv3kxderfxesrue@tp.flokli.de \
--to=flokli@flokli.de \
--cc=benjamin.tissoires@redhat.com \
--cc=iam@valdikss.org.ru \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®