From: Rob Landley <rob@landley.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: dri-devel@lists.freedesktop.org,
Linus Torvalds <torvalds@linux-foundation.org>,
David Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm: fix new kernel-doc warnings
Date: Tue, 05 Mar 2013 22:28:55 -0600 [thread overview]
Message-ID: <1362544135.7276.14@driftwood> (raw)
In-Reply-To: <51362680.3030203@infradead.org> (from rdunlap@infradead.org on Tue Mar 5 11:08:16 2013)
On 03/05/2013 11:08:16 AM, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix new kernel-doc warnings in drm_edid.c: convert doxygen(?) to
> kernel-doc to match the rest of the file's documentation.
I've been feeding this stuff through trivial@kernel.org. (I just got my
kernel.org account re-enabled yesterday, and hope to set up a tree to
feed into linux-next this weekend, but this is probably still trivial@
material anyway since it's scattered around the tree outside of the
documentation directory.)
Rob
prev parent reply other threads:[~2013-03-06 4:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 17:08 [PATCH] drm: fix new kernel-doc warnings Randy Dunlap
2013-03-06 4:28 ` Rob Landley [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=1362544135.7276.14@driftwood \
--to=rob@landley.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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 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.