All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 RESEND] iio: add kernel-doc for field @owner
Date: Sun, 7 Jan 2018 08:40:40 +1100	[thread overview]
Message-ID: <20180106214040.GA19656@eros> (raw)
In-Reply-To: <20180106130053.56401f8b@archlinux>

On Sat, Jan 06, 2018 at 01:00:53PM +0000, Jonathan Cameron wrote:
> On Sat,  6 Jan 2018 12:31:57 +1100
> "Tobin C. Harding" <me@tobin.cc> wrote:
> 
> > When building kernel documentation sphinx emits the following warning
> > 
> > 	warning: No description found for parameter 'owner'
> > 
> > Add description for struct member 'owner'.
> > 
> > Signed-off-by: Tobin C. Harding <me@tobin.cc>
> 
> This isn't a resend.  It's a version 2.  Please resend with the
> changes from v1 clearly stated.

Oh, you are right it should have been a version 2. The 'resend' referred
to the single cover letter I sent (forgot --to-cover --cc-cover flags to
git send-email).

> If you were resending you should say why as well in the cover letter!

My mistake, sloppy work.

> Jonathan

Thanks for your patience. Will fix up and re-send (as v3 ;)

thanks,
Tobin

  reply	other threads:[~2018-01-06 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06  1:31 [PATCH 0/2 RESEND] fix kernel-docs for struct iio_trigger Tobin C. Harding
2018-01-06  1:31 ` [PATCH 1/2 RESEND] iio: add kernel-doc for field @owner Tobin C. Harding
2018-01-06 13:00   ` Jonathan Cameron
2018-01-06 21:40     ` Tobin C. Harding [this message]
2018-01-06  1:31 ` [PATCH 2/2 RESEND] iio: add field identifier for @use_count kernel-doc 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=20180106214040.GA19656@eros \
    --to=me@tobin.cc \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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.