mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] regulator: kerneldoc cleanups
Date: Mon, 05 Jan 2009 12:04:13 +0000	[thread overview]
Message-ID: <1231157053.11643.138.camel@vega.slimlogic.co.uk> (raw)
In-Reply-To: <20081231125114.GC6596@sirena.org.uk>

On Wed, 2008-12-31 at 12:51 +0000, Mark Brown wrote:
> This patch series cleans up the kerneldoc for the regulator API and adds
> a brief DocBook manual for it, based heavily on the existing plain text
> documentation but much less complete.  I'm not sure that the manual
> itself is actually worthwhile, the main benefit from it is the generated 
> documentation rather than the text in the manual itself - I did the work
> to help with generating the earlier fixes.
> 
> It may be worth considering the first four patches for 2.6.29 as fixes,
> though it's questionable.

Applied.

Thanks

Liam


      parent reply	other threads:[~2009-01-05 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31 12:51 Mark Brown
2008-12-31 12:52 ` [PATCH 1/5] regulator: Remove extraneous kerneldoc annotations Mark Brown
2008-12-31 12:52   ` [PATCH 2/5] regulator: Clean up kerneldoc warnings Mark Brown
2008-12-31 12:52     ` [PATCH 3/5] regulator: Add missing kerneldoc Mark Brown
2008-12-31 12:52       ` [PATCH 4/5] regulator: Fix some kerneldoc rendering issues Mark Brown
2008-12-31 12:52         ` [PATCH 5/5] regulator: Add basic DocBook manual Mark Brown
2009-01-05 12:04 ` Liam Girdwood [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=1231157053.11643.138.camel@vega.slimlogic.co.uk \
    --to=lrg@slimlogic.co.uk \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@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®