From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] omap fixes against v3.16-rc1
Date: Mon, 7 Jul 2014 01:10:11 -0700 [thread overview]
Message-ID: <20140707081011.GG28884@atomide.com> (raw)
In-Reply-To: <CAOesGMjT+Sk+EbV40GCtM5GryqbJ7mTYVZRVLc1iCksGYG=kSQ@mail.gmail.com>
* Olof Johansson <olof@lixom•net> [140705 12:46]:
> On Fri, Jul 4, 2014 at 11:06 PM, Olof Johansson <olof@lixom•net> wrote:
> > Hi,
> >
> > On Fri, Jul 4, 2014 at 9:47 PM, Olof Johansson <olof@lixom•net> wrote:
> >> On Mon, Jun 30, 2014 at 12:08:57AM -0700, Tony Lindgren wrote:
> >>> * Tony Lindgren <tony@atomide•com> [140617 08:01]:
> >>> > The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
> >>> >
> >>> > Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
> >>> >
> >>> > are available in the git repository at:
> >>> >
> >>> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.16/fixes-against-rc1
> >>> >
> >>> > for you to fetch changes up to edc56f871eefbc56baf1fd981eeff35ef447925c:
> >>> >
> >>> > ARM: dts: dra7-evm: remove interrupt binding (2014-06-17 01:22:55 -0700)
> >>
> >> Merged. Apologies for the delay, I was planning on handling this earleir this
> >> week. I'll send this up tonight or tomorrow.
> >
> > Hmm. for-next with this merged in stopped omap5uevm from booting
> > (Can't find mmcblk1 which I keep the rootfs on), see
> > http://arm-soc.lixom.net/bootlogs/arm-soc/v3.16-rc1-76-gf5ee1b1/. One
> > of the three configs had a DHCP timeout, I'm going to rebuild the
> > network here to reduce the frequency of those.
> >
> > I'll try bisecting tomorrow. Not sending it up with this known
> > breakage, hopefully it's something simple.
>
> Hmm, this fixes branch + current mainline (or -rc3) seems fine, while
> the -rc1 base we used to have does not. In other words, it seems OK to
> send up for merge.
>
> Note that the OMAP branch by itself doesn't boot on this machine, so
> bisectability is lost for a bit. Not quite as worried about it since
> it's not in the merge window, so we should be OK.
Sorry just saw these messages. The MMC regulator issue was a known
problem with v3.16-rc1 unrelated to arm-soc tree that got fixed
already in the mainline kernel but was not yet merged to the mainline
kernel few weeks ago when I made this branch.
Regards,
Tony
prev parent reply other threads:[~2014-07-07 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 14:58 [GIT PULL] omap fixes against v3.16-rc1 Tony Lindgren
2014-06-30 7:08 ` Tony Lindgren
2014-07-05 4:47 ` Olof Johansson
2014-07-05 6:06 ` Olof Johansson
2014-07-05 19:44 ` Olof Johansson
2014-07-07 8:10 ` Tony Lindgren [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=20140707081011.GG28884@atomide.com \
--to=tony@atomide$(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