From: Linus Walleij <linus.walleij@linaro.org>
To: marek.behun@nic.cz
Cc: Lee Jones <lee.jones@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH mfd+gpio] Request (Linus Walleij + Lee Jones)
Date: Wed, 5 Sep 2018 11:36:39 +0200 [thread overview]
Message-ID: <CACRpkda8iVV6-J14L95cioJEL2eGSra9uNbPL19F6N7ijnjZiA@mail.gmail.com> (raw)
In-Reply-To: <20180830164743.63c6e27d@nic.cz>
On Thu, Aug 30, 2018 at 4:48 PM Marek Behun <marek.behun@nic.cz> wrote:
> Hi Linus and Lee,
> these two patches touch two different subsystems (mfd + gpio) and
> should be applyied one after another (the gpio part is dependant on the
> mfd part).
> The patches are based on mfd-next-4.19. I can send another copy based
> on gpio/devel.
> Could you two, Linus and Lee, work together on applying these patches?
> I don't know how this is usually solved...
If they need to go into the same merge window this is usually solved
by me ACKing the GPIO patches and Lee applying all of it to
the MFD tree then providing an immutable git branch to me if
I need the same changes in my tree.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-09-05 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 14:41 [PATCH mfd+gpio 1/2] drivers: mfd: Add support for Moxtet bus Marek Behún
2018-08-30 14:41 ` [PATCH mfd+gpio 2/2] drivers: gpio: Add support for GPIOs over " Marek Behún
2018-09-05 10:07 ` Linus Walleij
2018-09-05 10:07 ` Linus Walleij
2018-08-30 14:47 ` [PATCH mfd+gpio] Request (Linus Walleij + Lee Jones) Marek Behun
2018-09-05 9:36 ` Linus Walleij [this message]
2018-09-01 10:45 ` [PATCH mfd+gpio 1/2] drivers: mfd: Add support for Moxtet bus Dan Carpenter
2018-09-01 10:45 ` Dan Carpenter
2018-09-11 14:43 ` Lee Jones
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=CACRpkda8iVV6-J14L95cioJEL2eGSra9uNbPL19F6N7ijnjZiA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.behun@nic.cz \
/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.