mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, andrew@lunn.ch, daniel@iogearbox.net,
	edumazet@google.com, jakub.kicinski@netronome.com,
	brouer@redhat.com, linux@rasmusvillemoes.dk,
	john.fastabend@gmail.com, me@tobin.cc, idosch@mellanox.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] Kernel doc fixes for networking
Date: Tue, 23 Jan 2018 11:07:36 -0500 (EST)	[thread overview]
Message-ID: <20180123.110736.450396228712617945.davem@davemloft.net> (raw)
In-Reply-To: <20180123031428.4266-1-f.fainelli@gmail.com>

From: Florian Fainelli <f.fainelli@gmail.com>
Date: Mon, 22 Jan 2018 19:14:24 -0800

> This patch series fixes kernel doc warnings found while running make htmldocs
> pertaining to the networking subsystem. There is a finaly set of warnings due
> to PHYLINK which I have not been able to resolve yet.
> 
> The last patch could thereoteically be applied to 'net' since the commit
> referenced by the Fixes: tag is present in v4.15-rcX.

Series applied to net-next, thanks Florian.

I'll defer on the 'net' one, it's already really late in the game and only
super critical fixes should be submitted there at this point.

Thanks.

      parent reply	other threads:[~2018-01-23 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  3:14 Florian Fainelli
2018-01-23  3:14 ` [PATCH net-next 1/4] net: core: Fix kernel-doc for carrier_* attributes Florian Fainelli
2018-01-25  0:25   ` kbuild test robot
2018-01-23  3:14 ` [PATCH net-next 2/4] net: phy: sfp: Fix kernel doc warning Florian Fainelli
2018-01-23  3:14 ` [PATCH net-next 3/4] net: core: Fix kernel-doc for call_netdevice_notifiers_info() Florian Fainelli
2018-01-23  3:14 ` [PATCH net-next 4/4] net: core: Fix kernel-doc for netdev_upper_link() Florian Fainelli
2018-01-23 16:07 ` David Miller [this message]

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=20180123.110736.450396228712617945.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=john.fastabend@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=me@tobin.cc \
    --cc=netdev@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®