From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
johannes@sipsolutions.net
Subject: Re: [PATCH] docs: kernel-doc: fix parsing of arrays
Date: Thu, 29 Mar 2018 15:47:02 -0600 [thread overview]
Message-ID: <20180329154702.5df6c7bc@lwn.net> (raw)
In-Reply-To: <d5892e146872e40717117da6cc01e57525a063d2.1522335536.git.mchehab@s-opensource.com>
On Thu, 29 Mar 2018 10:58:59 -0400
Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> The logic with parses array has a bug that prevents it to
> parse arrays like:
> struct {
> ...
> struct {
> u64 msdu[IEEE80211_NUM_TIDS + 1];
> ...
> ...
>
> Fix the parser to accept it.
Applied, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-03-29 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 14:58 [PATCH] docs: kernel-doc: fix parsing of arrays Mauro Carvalho Chehab
2018-03-29 21:47 ` Jonathan Corbet [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=20180329154702.5df6c7bc@lwn.net \
--to=corbet@lwn.net \
--cc=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.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;
as well as URLs for NNTP newsgroup(s).