mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "Tobin C. Harding" <me@tobin.cc>, Jonathan Corbet <corbet@lwn.net>
Cc: "David S. Miller" <davem@davemloft.net>,
	linux-doc@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Documentation: e100: Use correct heading adornment
Date: Fri, 22 Jun 2018 09:44:43 -0700	[thread overview]
Message-ID: <c84fddcce0c977fd945873fec5d64e96f25993db.camel@intel.com> (raw)
In-Reply-To: <20180622003708.31848-2-me@tobin.cc>

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On Fri, 2018-06-22 at 10:37 +1000, Tobin C. Harding wrote:
> Recently documentation file was converted to rst.  The document title
> has the incorrect heading adornment.  From kernel docs:
> 
>         * Please stick to this order of heading adornments:
> 
>           1. ``=`` with overline for document title::
> 
>                ==============
>                Document title
>                ==============
> 
> Add  overline heading adornment to document title.
> 
> Fixes commit (85d63445f411 Documentation: e100: Update the Intel
> 10/100 driver doc)
> 
> CC: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Signed-off-by: Tobin C. Harding <me@tobin.cc>

Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-06-22 16:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  0:37 [PATCH 0/4] docs: e100[0] fix build errors Tobin C. Harding
2018-06-22  0:37 ` [PATCH 1/4] Documentation: e100: Use correct heading adornment Tobin C. Harding
2018-06-22 16:44   ` Jeff Kirsher [this message]
2018-06-22  0:37 ` [PATCH 2/4] Documentation: e1000: " Tobin C. Harding
2018-06-22 16:45   ` Jeff Kirsher
2018-06-22  0:37 ` [PATCH 3/4] Documentation: e100: Fix docs build error Tobin C. Harding
2018-06-22 16:46   ` Jeff Kirsher
2018-06-22  0:37 ` [PATCH 4/4] Documentation: e1000: " Tobin C. Harding
2018-06-22 16:47   ` Jeff Kirsher
2018-06-22 16:44 ` [PATCH 0/4] docs: e100[0] fix build errors Jeff Kirsher
2018-06-23  1:38   ` David Miller
2018-06-22 20:22 ` Randy Dunlap
2018-06-24 23:41   ` Tobin C. Harding
2018-06-25  1:11     ` Kirsher, Jeffrey T
2018-06-25  2:06       ` Tobin C. Harding

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=c84fddcce0c977fd945873fec5d64e96f25993db.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®