From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Om Prakash <omprakash.pal@stericsson.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] mfd/stmpe: fix missing kerneldoc
Date: Mon, 4 Jul 2011 17:25:34 +0200 [thread overview]
Message-ID: <20110704152534.GL3021@sortiz-mobl> (raw)
In-Reply-To: <1309161262-16670-1-git-send-email-linus.walleij@stericsson.com>
Hi Linus,
On Mon, Jun 27, 2011 at 09:54:22AM +0200, Linus Walleij wrote:
> From: Om Prakash <omprakash.pal@stericsson.com>
>
> Generating kerneldoc for STMPE result in warnings, so fix this by
> adding missing documentation.
Thanks, patch applied.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-07-04 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 7:54 [PATCH] mfd/stmpe: fix missing kerneldoc Linus Walleij
2011-07-04 15:25 ` Samuel Ortiz [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=20110704152534.GL3021@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omprakash.pal@stericsson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox