All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the irqchip tree
Date: Tue, 08 Jun 2021 08:36:12 +0100	[thread overview]
Message-ID: <87h7i8zu37.wl-maz@kernel.org> (raw)
In-Reply-To: <20210608092148.4304e644@canb.auug.org.au>

Hi Stephen,

On Tue, 08 Jun 2021 00:21:48 +0100,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi all,
> 
> After merging the irqchip tree, yesterday's linux-next build (htmldocs)
> produced this warning:
> 
> include/linux/interrupt.h:131: warning: Function parameter or member 'desc' not described in 'irqaction'
> 
> Introduced by commit
> 
>   bb33916b527f ("genirq: Replace irqaction:irq with a pointer to the irqdesc")

Huhuh... This patch should have never made it in -next. I must have
messed up once more.

/me goes and rebuild the branch now, which will also get rid of the
fixups lacking SoBs.

Thanks for the heads up,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2021-06-08  7:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 23:21 linux-next: build warning after merge of the irqchip tree Stephen Rothwell
2021-06-08  7:36 ` Marc Zyngier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-13  9:44 Stephen Rothwell
2021-09-03  6:47 ` Stephen Rothwell
2021-09-03  9:00   ` Marc Zyngier
2021-06-15 11:01 Stephen Rothwell
2021-07-08  2:18 ` Stephen Rothwell
2021-07-08  8:10   ` Marc Zyngier
2021-07-08 12:50     ` Stephen Rothwell
2021-07-08 16:32       ` Marc Zyngier
2021-07-08 21:41         ` Stephen Rothwell
2018-12-14  3:44 Stephen Rothwell
2018-12-15  9:16 ` Marc Zyngier
2014-11-27  6:28 Stephen Rothwell

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=87h7i8zu37.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.