From: Christoph Hellwig <hch@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>, samr <sam@ravnborg.org>,
Roland McGrath <roland@redhat.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] kernel-doc: allow structs whose members are all private
Date: Mon, 15 Sep 2008 13:26:48 -0400 [thread overview]
Message-ID: <20080915172648.GA2856@infradead.org> (raw)
In-Reply-To: <20080915100229.cf32f74e.randy.dunlap@oracle.com>
On Mon, Sep 15, 2008 at 10:02:29AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix kernel-doc to handle structs whose members are all private;
> otherwise invalid XML is generated:
What's supposed to be a private member?
next prev parent reply other threads:[~2008-09-15 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 17:02 Randy Dunlap
2008-09-15 17:26 ` Christoph Hellwig [this message]
2008-09-15 17:31 ` Randy Dunlap
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=20080915172648.GA2856@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=roland@redhat.com \
--cc=sam@ravnborg.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®