From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Sachin Kamat'" <sachin.kamat@linaro.org>,
"'Linus Walleij'" <linus.walleij@linaro.org>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
"'linux-samsung-soc'" <linux-samsung-soc@vger.kernel.org>
Subject: RE: Failure due to missing (Exynos related) pinctrl patch
Date: Tue, 29 Jan 2013 20:08:07 -0800 [thread overview]
Message-ID: <076401cdfe9f$6a0f5fa0$3e2e1ee0$@samsung.com> (raw)
In-Reply-To: <CAK9yfHwav_u3mjVqNdX4kY=LyUW30vr6AMGUExfGKuJn2KH8qQ@mail.gmail.com>
Sachin Kamat wrote:
>
> >> This patch is required along with the
> >> patch "gpio: samsung: fix pinctrl condition for exynos and exynos5440"
> >> (mainline commit Id: e4a5da51) which has already made it into
> >> mainline. Without the missing patch we get the following boot up
> >> warnings and subsequent failures with dt boot on 4412 based board:
> >
> > Hm I didn't realize there was a dependency between these
> > patches, oh well, better get the pull for the pinctrl tree finished
> > off then...
>
> Ideally those 2 patches should have been squashed together.
>
Err, Sachin, what are you talking about? As you said, one patch has been
merged into the mainline, so how does it can be squashed? In this case, just
applying the other patch into pinctrl-fixes is enough.
Thanks.
- Kukjin
next prev parent reply other threads:[~2013-01-30 4:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 5:10 Sachin Kamat
2013-01-29 6:20 ` Kukjin Kim
2013-01-29 22:25 ` Linus Walleij
2013-01-30 3:54 ` Sachin Kamat
2013-01-30 4:08 ` Kukjin Kim [this message]
2013-01-30 4:10 ` Sachin Kamat
2013-01-30 9:48 ` Linus Walleij
2013-01-30 10:15 ` Sachin Kamat
2013-01-31 13:59 ` Linus Walleij
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='076401cdfe9f$6a0f5fa0$3e2e1ee0$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sachin.kamat@linaro.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
Powered by JetHome