From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Kosina <jikos@kernel.org>,
Walt Holman <waltholman09@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the hid tree
Date: Fri, 10 Feb 2023 14:37:28 +0100 [thread overview]
Message-ID: <CAO-hwJJcXj7QT-N3Nmaua9C4gw=kqt0qMz_RBTskrZxgHqF-AA@mail.gmail.com> (raw)
In-Reply-To: <20230210084207.4d02d107@canb.auug.org.au>
Hi Stephen,
On Thu, Feb 9, 2023 at 10:42 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Commit
>
> f1fc9fbc8394 ("HID: Add support for Logitech G923 Xbox Edition steering wheel")
>
> is missing a Signed-off-by from its author.
>
> This is just a typo - "Signed-of-by".
Alright, force pushed an update of the whole for-6.3/logitech branch
with both this typo fix and the missing-12-chars-for-fixes-tag that
was in that branch too.
Also force pushed for-next, which cleans a little bit everything, with
a check that the old for-next branch and the new one have the exact
same content.
Cheers,
Benjamin
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2023-02-10 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 21:42 linux-next: Signed-off-by missing for commit in the hid tree Stephen Rothwell
2023-02-10 13:37 ` Benjamin Tissoires [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 21:32 Stephen Rothwell
2024-01-03 2:42 ` Vicki Pfau
2022-07-25 11:43 Stephen Rothwell
2021-08-21 0:46 Stephen Rothwell
2020-06-24 7:52 Stephen Rothwell
2020-06-24 7:56 ` Jiri Kosina
2020-06-20 21:51 Stephen Rothwell
2020-06-22 7:59 ` Cristian Klein
2018-05-15 21:17 Stephen Rothwell
2018-05-16 14:21 ` Rodrigo Rivas Costa
2018-05-17 0:46 ` 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='CAO-hwJJcXj7QT-N3Nmaua9C4gw=kqt0qMz_RBTskrZxgHqF-AA@mail.gmail.com' \
--to=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=waltholman09@gmail.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;
as well as URLs for NNTP newsgroup(s).