Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] Documentation fixes
Date: Fri, 06 Apr 2012 02:43:33 -0400 (EDT)	[thread overview]
Message-ID: <20120406.024333.2063598126722690725.davem@davemloft.net> (raw)
In-Reply-To: <1333672667.2652.22.camel@bwh-desktop.uk.solarflarecom.com>

From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 6 Apr 2012 01:37:47 +0100

> These changes update Documentation/networking/driver.txt and
> Documentation/networking/netdevices.txt to reflect the last 5 or so
> years of API changes (though no new features are documented).
> 
> They also remove documentation of a wrinkle in ethtool_ops that I
> recently fixed.
> 
> These could safely be applied to either net or net-next; they can't
> break anything but another 3 months of dust isn't going to make much
> difference.

Thanks for doing this work Ben, I've applied it all to 'net'.

      reply	other threads:[~2012-04-06  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06  0:37 [PATCH net-next 0/6] Documentation fixes Ben Hutchings
2012-04-06  6:43 ` 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=20120406.024333.2063598126722690725.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhutchings@solarflare.com \
    --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