mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, mawilcox@microsoft.com
Subject: Re: [PATCH 1/3] scripts/kernel-doc: Don't fail with status != 0 if error encountered with -none
Date: Wed, 29 Nov 2017 16:35:03 +0000	[thread overview]
Message-ID: <20171129163502.GB32356@arm.com> (raw)
In-Reply-To: <20171129091214.32437ea0@lwn.net>

On Wed, Nov 29, 2017 at 09:12:14AM -0700, Jonathan Corbet wrote:
> On Wed, 29 Nov 2017 15:20:03 +0000
> Will Deacon <will.deacon@arm.com> wrote:
> 
> > My bisect scripts starting running into build failures when trying to
> > compile 4.15-rc1 with the builds failing with things like:
> > 
> > drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c:2078: error: Cannot parse struct or union!
> > 
> > The line in question is actually just a #define, but after some digging
> > it turns out that my scripts pass W=1 and since commit 3a025e1d1c2ea
> > ("Add optional check for bad kernel-doc comments") that results in
> > kernel-doc running on each source file. The file in question has a
> > badly formatted comment immediately before the #define:
> > 
> > /**
> >  * struct brcmf_skbuff_cb reserves first two bytes in sk_buff::cb for
> >  * bus layer usage.
> >  */
> > 
> > which causes the regex in dump_struct to fail (lack of braces following
> > struct declaration) and kernel-doc returns 1, which causes the build
> > to fail.
> > 
> > Fix the issue by always returning 0 from kernel-doc when invoked with
> > -none. It successfully generates no documentation, and prints out any
> > issues.
> 
> That seems like a worthy fix.  I can take this one and ship it up with a
> few other docs fixes in the near future, thanks.

Brill, cheers Jon. It had me extremely confused for a while until I figured
out the warning wasn't coming from GCC :)

Will

      reply	other threads:[~2017-11-29 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 15:20 Will Deacon
2017-11-29 15:20 ` [PATCH 2/3] brcmfmac: Fix comment syntax Will Deacon
2017-11-29 15:20 ` [PATCH 3/3] drm/ttm: " Will Deacon
2017-11-29 16:12 ` [PATCH 1/3] scripts/kernel-doc: Don't fail with status != 0 if error encountered with -none Jonathan Corbet
2017-11-29 16:35   ` Will Deacon [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=20171129163502.GB32356@arm.com \
    --to=will.deacon@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mawilcox@microsoft.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

Powered by JetHome