All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marc Zyngier <maz@kernel.org>
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: Thu, 8 Jul 2021 22:50:37 +1000	[thread overview]
Message-ID: <20210708225037.4980f159@canb.auug.org.au> (raw)
In-Reply-To: <87im1l2plp.wl-maz@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

Hi Marc,

On Thu, 08 Jul 2021 09:10:10 +0100 Marc Zyngier <maz@kernel.org> wrote:
>
> Hmmm... I've had a fix for this sitting in irqchip-fixes for some
> time. But I now realise that this branch is not included in -next
> while tip tracks it.
> 
> Any chance you could add [1] to -next in the future?
> 
> Thanks,
> 
> 	M.
> 
> [1] git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/irqchip-fixes

So I assume this a branch of bug fixes for the current release, right?
In which case I will add it tomorrow.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-07-08 12:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 11:01 linux-next: build warning after merge of the irqchip tree Stephen Rothwell
2021-07-08  2:18 ` Stephen Rothwell
2021-07-08  8:10   ` Marc Zyngier
2021-07-08 12:50     ` Stephen Rothwell [this message]
2021-07-08 16:32       ` Marc Zyngier
2021-07-08 21:41         ` Stephen Rothwell
  -- 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-07 23:21 Stephen Rothwell
2021-06-08  7:36 ` Marc Zyngier
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=20210708225037.4980f159@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maz@kernel.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.