From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] mfd: exynos-lpass: Pinctrl dependency
Date: Tue, 4 Apr 2017 10:50:54 +0100 [thread overview]
Message-ID: <20170404095054.7m6nf6bxweskabuu@dell> (raw)
In-Reply-To: <CAJKOXPeVOMBZxXeh7=oXbgnxSrUtHa86eAtP2BppY=G4Uygarg@mail.gmail.com>
On Tue, 04 Apr 2017, Krzysztof Kozlowski wrote:
> On Mon, Apr 3, 2017 at 12:18 PM, Lee Jones <lee.jones@linaro.org> wrote:
> > On Tue, 28 Mar 2017, Krzysztof Kozlowski wrote:
> >
> >>
> >> Hi Lee,
> >>
> >>
> >> This is dependency for mfd/exynos-lpass driver changes from Marek Szyprowski.
> >> That's a material for v4.12 and I will be pushing this later to Linus Walleij.
> >
> > This does not work, and *may* still break.
> >
> > The only way to guarantee the order of the patches is to have them
> > *all* as part of the pull-request. Not just some of them.
>
> What do you mean exactly? If these two patches come through my tree
> first, then everything will work fine because they do not break any
> other stuff.
>
> If you pull it and apply the rest on top, then it should also work
> without problems because your history will contain everything needed
> in proper order.
>
> In both cases bisectability is preserved. Did I missed something?
Okay, so you're suggesting that I rebase MFD *on-top* of your PR. That
does work for me because I insist on being able to re-work my tree at
any time. However, be aware that some Maintainers do not work this
way, thus *normally* you will have to send PR containing all of the
dependant patches.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-04-04 9:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170323080346eucas1p216eec41325d220774ecec05b397e83a6@eucas1p2.samsung.com>
2017-03-23 8:03 ` [PATCH v4 0/6] Pad retentions support for Exynos5433 Marek Szyprowski
2017-03-23 8:03 ` [PATCH v4 1/6] pinctrl: samsung: Ensure that pad retention is disabled on driver init Marek Szyprowski
2017-03-23 19:14 ` Krzysztof Kozlowski
2017-03-23 8:03 ` [PATCH v4 2/6] pinctrl: samsung: Add support for pad retention control for Exynos5433 SoCs Marek Szyprowski
2017-03-23 19:15 ` Krzysztof Kozlowski
2017-03-23 8:03 ` [PATCH v4 3/6] mfd: exynos-lpass: Remove pad retention control Marek Szyprowski
2017-04-11 12:02 ` Lee Jones
2017-04-19 11:00 ` Marek Szyprowski
2017-04-24 10:35 ` Lee Jones
2017-03-23 8:03 ` [PATCH v4 4/6] mfd: exynos-lpass: Add support for clocks Marek Szyprowski
2017-04-11 12:03 ` Lee Jones
2017-03-23 8:03 ` [PATCH v4 5/6] mfd: exynos-lpass: Add missing remove() function Marek Szyprowski
2017-04-11 12:03 ` Lee Jones
2017-03-23 8:03 ` [PATCH v4 6/6] mfd: exynos-lpass: Add runtime PM support Marek Szyprowski
2017-04-11 12:03 ` Lee Jones
2017-03-28 9:22 ` [PATCH v4 0/6] Pad retentions support for Exynos5433 Linus Walleij
2017-03-28 10:14 ` Krzysztof Kozlowski
2017-03-28 15:42 ` [GIT PULL] mfd: exynos-lpass: Pinctrl dependency Krzysztof Kozlowski
2017-04-03 10:18 ` Lee Jones
2017-04-04 8:23 ` Krzysztof Kozlowski
2017-04-04 9:50 ` Lee Jones [this message]
2017-04-04 9:57 ` Krzysztof Kozlowski
2017-04-11 11:57 ` Lee Jones
2017-04-11 11:59 ` 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=20170404095054.7m6nf6bxweskabuu@dell \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox