From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
msizanoen1 <msizanoen@qtmlabs.xyz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@google.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the net tree
Date: Mon, 29 Nov 2021 15:42:47 -0500 [thread overview]
Message-ID: <CAHmME9qSBPQ98nOy_xkjeHfJ9mCm4JWbWQTx3M6wB21YHrzjBg@mail.gmail.com> (raw)
In-Reply-To: <20211130073228.611fa87f@canb.auug.org.au>
Hi Stephen,
This is known. Please see the below-the-break comment in the original
patch submission:
https://lore.kernel.org/netdev/20211123124832.15419-1-Jason@zx2c4.com/
> The original author of this commit and commit message is anonymous and
> is therefore unable to sign off on it. Greg suggested that I do the sign
> off, extracting it from the bugzilla entry above, and post it properly.
> The patch "seems to work" on first glance, but I haven't looked deeply
> at it yet and therefore it doesn't have my Reviewed-by, even though I'm
> submitting this patch on the author's behalf. And it should probably get
> a good look from the v6 fib folks. The original author should be on this
> thread to address issues that come off, and I'll shephard additional
> versions that he has.
Jason
next prev parent reply other threads:[~2021-11-29 20:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 20:32 linux-next: Signed-off-by missing for commit in the net tree Stephen Rothwell
2021-11-29 20:42 ` Jason A. Donenfeld [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-01 15:26 Stephen Rothwell
2023-12-10 22:09 Stephen Rothwell
2023-05-14 22:44 Stephen Rothwell
2023-03-06 21:37 Stephen Rothwell
2023-03-06 22:16 ` Heiner Kallweit
2023-03-07 0:52 ` Stephen Rothwell
2023-03-07 1:32 ` Jakub Kicinski
2023-01-11 21:07 Stephen Rothwell
2022-04-25 21:53 Stephen Rothwell
2021-05-19 21:46 Stephen Rothwell
2021-05-05 22:14 Stephen Rothwell
2020-09-20 19:50 Stephen Rothwell
2020-05-31 17:57 Stephen Rothwell
2019-12-07 7:18 Stephen Rothwell
2019-11-17 20:11 Stephen Rothwell
2019-11-13 20:21 Stephen Rothwell
2019-11-14 8:25 ` Marc Kleine-Budde
2019-10-15 20:36 Stephen Rothwell
2019-08-05 21:38 Stephen Rothwell
2019-08-05 21:43 ` David Miller
2019-04-13 8:30 Stephen Rothwell
2019-04-13 10:34 ` David Howells
2019-03-19 5:21 Stephen Rothwell
2019-03-18 4:50 Stephen Rothwell
2019-01-11 3:48 Stephen Rothwell
2019-01-11 6:10 ` Heiner Kallweit
2019-01-11 6:27 ` Frank Wunderlich
2019-01-11 13:58 ` Andrew Lunn
2018-11-21 5:04 Stephen Rothwell
2018-11-20 5:15 Stephen Rothwell
2018-11-20 8:25 ` Xin Long
2018-11-20 17:17 ` David Miller
2018-07-04 21:49 Stephen Rothwell
2018-05-10 21:17 Stephen Rothwell
2018-05-11 1:30 ` Hangbin Liu
2018-04-29 21:18 Stephen Rothwell
2018-02-08 22:18 Stephen Rothwell
2018-02-08 3:27 Stephen Rothwell
2017-09-19 4:43 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=CAHmME9qSBPQ98nOy_xkjeHfJ9mCm4JWbWQTx3M6wB21YHrzjBg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=gregkh@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=msizanoen@qtmlabs.xyz \
--cc=netdev@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 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.