All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next 0/4] mei: docmentation cleanup
Date: Tue, 23 Sep 2014 23:02:48 -0700	[thread overview]
Message-ID: <20140924060248.GA26703@kroah.com> (raw)
In-Reply-To: <1411286416-15339-1-git-send-email-tomas.winkler@intel.com>

On Sun, Sep 21, 2014 at 11:00:12AM +0300, Tomas Winkler wrote:
> Overall documentation formating fix and other collateral 
> fixes.
> 

Didn't apply :(

      parent reply	other threads:[~2014-09-24  8:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-21  8:00 [char-misc-next 0/4] mei: docmentation cleanup Tomas Winkler
2014-09-21  8:00 ` [char-misc-next 1/4] mei: trivial: fix errors in prints in comments Tomas Winkler
2014-09-21  8:00 ` [char-misc-next 2/4] mei: drop me_client_presentation_num Tomas Winkler
2014-09-21  8:00 ` [char-misc-next 3/4] mei: fix KDoc documentation formatting Tomas Winkler
2014-09-21  8:00 ` [char-misc-next 4/4] mei: fix kernel-doc warnings Tomas Winkler
2014-09-24  6:02 ` Greg KH [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=20140924060248.GA26703@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    /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.