From: Jakub Kicinski <kuba@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the net-next tree
Date: Tue, 5 Sep 2023 16:44:06 -0700 [thread overview]
Message-ID: <20230905164406.04ff113c@kernel.org> (raw)
In-Reply-To: <20230906085543.1c19079a@canb.auug.org.au>
On Wed, 6 Sep 2023 08:55:43 +1000 Stephen Rothwell wrote:
> > Documentation/networking/kapi:144: include/linux/phylink.h:614: WARNING: Inline literal start-string without end-string.
> > Documentation/networking/kapi:144: include/linux/phylink.h:644: WARNING: Inline literal start-string without end-string.
>
> These have not :-(
Fix posted. I thought it was about phylink_mode_*() but apparently
the warnings are always reported with line num of the first line of
the paragraph, and the problem was actually in %PHYLINK_PCS_NEG_*.
Humpf.
next prev parent reply other threads:[~2023-09-05 23:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 6:29 linux-next: build warnings after merge of the net-next tree Stephen Rothwell
2023-09-05 22:55 ` Stephen Rothwell
2023-09-05 23:44 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 8:31 Stephen Rothwell
2025-08-01 4:42 ` Stephen Rothwell
2025-08-11 9:53 ` Paolo Abeni
2025-08-12 4:36 ` Stephen Rothwell
2024-11-04 5:30 Stephen Rothwell
2023-12-04 4:47 Stephen Rothwell
2023-09-18 3:15 Stephen Rothwell
2023-09-18 7:43 ` Bagas Sanjaya
2023-06-13 6:31 Stephen Rothwell
2023-06-20 16:15 ` Jakub Kicinski
2023-06-20 23:12 ` Saeed Mahameed
2022-11-14 7:31 Stephen Rothwell
2022-11-14 8:00 ` Akira Yokosawa
2021-06-15 11:23 Stephen Rothwell
2021-06-15 11:12 Stephen Rothwell
2021-03-18 6:22 Stephen Rothwell
2021-02-18 20:52 Stephen Rothwell
2021-02-19 8:44 ` Stephen Rothwell
2021-02-19 14:57 ` Kalle Valo
2020-12-14 9:10 Stephen Rothwell
2020-12-21 1:28 ` Stephen Rothwell
2021-01-05 6:19 ` Stephen Rothwell
2019-11-05 1:45 Stephen Rothwell
2017-03-20 6:07 Stephen Rothwell
2017-01-18 0:37 Stephen Rothwell
2016-11-22 1:22 Stephen Rothwell
2016-11-22 1:28 ` Florian Fainelli
2016-11-22 8:23 ` Thomas Petazzoni
2015-06-20 13:12 Stephen Rothwell
2015-06-20 13:12 ` Stephen Rothwell
2015-06-20 17:40 ` Florian Westphal
2015-06-20 17:40 ` Florian Westphal
2015-06-20 18:31 ` Pablo Neira Ayuso
2015-06-20 18:31 ` Pablo Neira Ayuso
2015-05-14 7:12 Stephen Rothwell
2015-05-14 7:12 ` Stephen Rothwell
2015-05-14 14:47 ` Willem de Bruijn
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=20230905164406.04ff113c@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--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.