From: kgene.kim@samsung•com (Kukjin Kim)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 2nd 3/5] Samsung defconfig update for v3.14
Date: Sat, 04 Jan 2014 11:04:24 +0900 [thread overview]
Message-ID: <22f401cf08f1$4a6ece30$df4c6a90$@samsung.com> (raw)
In-Reply-To: <CAOesGMhEVQi7kw9WW+nV3MB=7rz0TK==wccAKFePrm-Ub=H=Bw@mail.gmail.com>
Olof Johansson wrote:
>
> On Tue, Dec 31, 2013 at 8:17 AM, Mark Brown <broonie@kernel•org> wrote:
> > On Sat, Dec 28, 2013 at 07:48:26PM -0800, Olof Johansson wrote:
> >> On Sat, Dec 28, 2013 at 7:44 PM, Olof Johansson <olof@lixom•net> wrote:
> >
> >> > The regulator driver causes build breaks. Really, nobody checks these
> >> > things before sending patches or merge requests?
> >
> >> > Having exynos_defconfig broken in arm-soc isn't an alternative. So I
> >> > dropped this branch again. If the regulator driver gets fixed in -rc
> >> > then we can probably merge it before the merge window, otherwise
> we'll
> >> > have to merge the defconfig change after the regulator fix goes in
> for
> >> > the 3.14 merge window.
> >
> >> Ah, I guess the fix went in after -rc4, which is the latest -rc that
> >> we have in for-next today. I'll bring for-next forward and merge this
> >> in.
> >
> >> Still, it's odd that you were able to test your branch before sending
> it in.
> >
> > The build breakage was only introduced in -rc4 - a MFD/RTC change went
> > in via Andrew's tree so it got no exposure in -next before it showed up
> > in Linus' tree which wasn't good. The fix was in by -rc5, looking at
> > the date on the pull request I expect that any testing against -next (as
> > opposed to arm-soc) would've been OK and since the branch is based on
> > -rc1 it'd have tested out by itself as well.
>
>
> Ah, yeah, that explains it. Thanks for the clarification.
>
Sorry for late response and Mark, thanks for your response ;-)
Olof, I have not seen regarding problem in my tree before my pull-request so
I didn't know but I will look at -next and arm-soc more closely.
Thanks.
Kukjin
prev parent reply other threads:[~2014-01-04 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 18:23 [GIT PULL 2nd 3/5] Samsung defconfig update for v3.14 Kukjin Kim
2013-12-28 23:15 ` Olof Johansson
2013-12-29 3:44 ` Olof Johansson
2013-12-29 3:48 ` Olof Johansson
2013-12-31 16:17 ` Mark Brown
2013-12-31 18:02 ` Olof Johansson
2014-01-04 2:04 ` Kukjin Kim [this message]
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='22f401cf08f1$4a6ece30$df4c6a90$@samsung.com' \
--to=kgene.kim@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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