All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jianqun Xu <jay.xu@rock-chips.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the pinctrl tree with the irqchip tree
Date: Wed, 18 Aug 2021 20:59:22 +0100	[thread overview]
Message-ID: <87pmuazfqd.wl-maz@kernel.org> (raw)
In-Reply-To: <CACRpkdYNnrk35yA5u8wxMyOquxSovr9xTeYjDd61K=38Vyby4g@mail.gmail.com>

On Tue, 17 Aug 2021 21:14:35 +0100,
Linus Walleij <linus.walleij@linaro.org> wrote:
> 
> On Tue, Aug 17, 2021 at 12:04 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > Today's linux-next merge of the pinctrl tree got a conflict in:
> >
> >   drivers/pinctrl/pinctrl-rockchip.c
> >
> > between commit:
> >
> >   a9cb09b7be84 ("pinctrl: Bulk conversion to generic_handle_domain_irq()")
> >
> > from the irqchip tree and commit:
> >
> >   9ce9a02039de ("pinctrl/rockchip: drop the gpio related codes")
> >
> > from the pinctrl tree.
> >
> > I fixed it up (the latter removed the code changed by the former, so I
> > did that) and can carry the fix as necessary.
> 
> I have created an immutable branch for these changes:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=ib-rockchip
> 
> If it helps irqchip they can pull this in (and fix things on top if
> need be).

Cheers Linus, I've pulled this branch in and resolved the conflict
locally.

Thanks,

	M.

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

  reply	other threads:[~2021-08-18 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 10:04 linux-next: manual merge of the pinctrl tree with the irqchip tree Stephen Rothwell
2021-08-17 20:14 ` Linus Walleij
2021-08-18 19:59   ` Marc Zyngier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-21 22:32 broonie
2022-02-28  7:04 ` 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=87pmuazfqd.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=jay.xu@rock-chips.com \
    --cc=linus.walleij@linaro.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.