From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
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 drivers-x86 tree
Date: Tue, 17 Dec 2024 14:24:00 +0200 (EET) [thread overview]
Message-ID: <810e0861-bcbd-65ca-1d4b-ec06213d2f27@linux.intel.com> (raw)
In-Reply-To: <9166ecd7-7b73-4db6-9827-7e65fb06057b@t-8ch.de>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Mon, 16 Dec 2024, Thomas Weißschuh wrote:
> On 2024-12-17 07:17:48+1100, Stephen Rothwell wrote:
> > Commit
> >
> > f05a99b0d5f1 ("platform/x86: dell: dcdbas: Constify 'struct bin_attribute'")
> >
> > is missing a Signed-off-by from its author.
>
> thanks for the hint.
>
> Ilpo, do you think you can fold my Sign-off into the commit:
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Thanks for the heads up.
I've added the signoff into the commit in my review-ilpo-next branch
where from it will eventually propagate into the for-next branch.
--
i.
next prev parent reply other threads:[~2024-12-17 12:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 20:17 linux-next: Signed-off-by missing for commit in the drivers-x86 tree Stephen Rothwell
2024-12-16 21:38 ` Thomas Weißschuh
2024-12-17 12:24 ` Ilpo Järvinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-07 23:15 Stephen Rothwell
2023-06-08 9:02 ` Hans de Goede
2023-02-02 21:33 Stephen Rothwell
2023-02-03 9:06 ` Hans de Goede
2021-04-14 13:51 Stephen Rothwell
2021-04-14 13:55 ` Hans de Goede
2021-04-08 12:13 Stephen Rothwell
2021-04-08 14:18 ` Hans de Goede
2019-05-06 13:22 Stephen Rothwell
2019-05-06 14:50 ` Andy Shevchenko
2019-02-23 14:19 Stephen Rothwell
2019-02-23 17:10 ` Darren Hart
2019-02-23 17:52 ` Darren Hart
2019-02-23 22:56 ` Stephen Rothwell
2018-08-18 14:35 Stephen Rothwell
2018-08-19 8:21 ` Hans de Goede
2018-08-19 8:48 ` Stephen Rothwell
2018-06-01 11:36 Stephen Rothwell
2018-06-01 11:40 ` Andy Shevchenko
2018-06-01 12:08 ` Stephen Rothwell
2018-06-01 14:33 ` dvhart
2018-06-01 14:55 ` Andy Shevchenko
2018-06-01 14:38 ` dvhart
2018-06-01 15:26 ` Stephen Rothwell
2018-06-01 16:43 ` Darren Hart
2018-06-01 14:45 ` Andy Shevchenko
2017-08-02 20:37 Stephen Rothwell
2017-08-02 23:57 ` Darren Hart
2017-08-03 0:28 ` Stephen Rothwell
2017-08-03 1:06 ` Linus Torvalds
2017-08-03 15:50 ` Darren Hart
2017-08-05 21:58 ` Darren Hart
2017-08-16 23:21 ` Darren Hart
2017-08-24 20:56 ` Darren Hart
2017-08-04 17:44 ` Junio C Hamano
2017-08-04 17:47 ` Darren Hart
2017-08-03 8:17 ` Andy Shevchenko
2017-08-03 9:27 ` 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=810e0861-bcbd-65ca-1d4b-ec06213d2f27@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=markgross@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.