From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
Networking <netdev@vger.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 commits in the net-next tree
Date: Wed, 26 Jan 2022 22:50:09 +0000 [thread overview]
Message-ID: <YfHQIZ07stBQTNqm@shell.armlinux.org.uk> (raw)
In-Reply-To: <20220127075702.1b0b73c2@canb.auug.org.au>
On Thu, Jan 27, 2022 at 07:57:02AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 04a0683f7db4 ("net: stmmac: convert to phylink_generic_validate()")
> f4c296c90976 ("net: stmmac: remove phylink_config.pcs_poll usage")
> d194923d51c9 ("net: stmmac: fill in supported_interfaces")
> 92c3807b9ac3 ("net: stmmac: convert to phylink_get_linkmodes()")
> be6ec5b70266 ("net: xpcs: add support for retrieving supported interface modes")
>
> are missing a Signed-off-by from their author.
Hi Stephen,
Sigh, this is more vim stupidity. The commits _look_ fine in vim and
look fine in git log on an 80 column display, but that is because the
"Tested-by" line somehow ended up with the perfect amount of space
characters to make it so.
This is not the first time this has happened - it keeps happening, and
I've no clue why it keeps happening, other than rediculous vi behaviour.
I'm sorry, but I don't see any solution to it at the moment. Maybe
someone can suggest something that (a) prevents it happening when I
paste in the Tested-by line, and (b) makes vim show when lines in a
commit message are longer than 80 characters?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-01-26 22:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 20:57 linux-next: Signed-off-by missing for commits in the net-next tree Stephen Rothwell
2022-01-26 22:50 ` Russell King (Oracle) [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-06 20:22 Stephen Rothwell
2022-03-07 23:02 ` Jakub Kicinski
2022-03-07 23:19 ` Stephen Rothwell
2022-03-07 23:24 ` Jakub Kicinski
2021-08-21 3:08 Stephen Rothwell
2021-08-21 6:37 ` Sven Eckelmann
2020-03-10 10:01 Stephen Rothwell
2020-03-10 23:57 ` Saeed Mahameed
2020-04-13 0:05 ` Stephen Rothwell
2020-04-16 1:58 ` Saeed Mahameed
2019-11-25 7:28 Stephen Rothwell
2019-11-25 7:35 ` Daniel Borkmann
2019-08-15 21:53 Stephen Rothwell
2019-08-15 22:06 ` Gerd Rausch
2019-08-16 9:15 ` Andy Grover
2019-08-16 12:45 ` Chris Mason
2019-08-16 14:10 ` Gerd Rausch
2019-08-16 14:31 ` Stephen Rothwell
2018-12-09 21:00 Stephen Rothwell
2018-12-09 21:11 ` Andrew Lunn
2018-12-09 21:33 ` Heiner Kallweit
2018-12-09 21:49 ` Andrew Lunn
2018-12-09 23:27 ` Sabrina Dubroca
2018-12-10 0:31 ` David Miller
2018-12-10 0:48 ` Stephen Rothwell
2018-12-10 0:54 ` David Miller
2018-12-10 2:05 ` Stephen Rothwell
2018-12-10 0:28 ` David Miller
2018-12-10 13:35 ` Andrew Lunn
2018-12-10 13:55 ` Sabrina Dubroca
2018-12-10 0:27 ` David Miller
2018-10-19 7:30 Stephen Rothwell
2018-04-02 2:30 Stephen Rothwell
2018-04-02 5:38 ` Johan Hedberg
2018-04-02 6:50 ` Stephen Rothwell
2018-03-02 4:52 Stephen Rothwell
2017-12-18 20:41 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=YfHQIZ07stBQTNqm@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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).