From: Tony Lindgren <tony@atomide.com>
To: Olof Johansson <olof@lixom.net>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"arm@kernel.org" <arm@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 2/4] omap changes for ti81xx devices and minimal dra62x j5eco-evm support
Date: Tue, 22 Dec 2015 17:47:57 -0800 [thread overview]
Message-ID: <20151223014756.GJ2793@atomide.com> (raw)
In-Reply-To: <CAOesGMjKaRcTHQ40p0pMUW-z1o9HZqEmon3fsFKe46QX82+gDA@mail.gmail.com>
Hi,
* Olof Johansson <olof@lixom.net> [151222 15:41]:
> On Tue, Dec 22, 2015 at 3:33 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Olof Johansson <olof@lixom.net> [151222 14:58]:
> >>
> >> I'm a little puzzled by how you chose to organize this branch. We usually
> >> ask for SoC enablement and new DT files separately. Is there a reason you
> >> couldn't split out the SoC pieces and include those in the soc branch, and
> >> leave the DT contents for this one?
> >
> > Hmm yeah I guess I kept all the 81xx stuff in a single branch because of the
> > earlier largeish set of 81xx fixes that had interlaced dts and SoC changes
> > that had to be in a specific order to keep system booting because of bugs in
> > the dts defined clocks.
> >
> > If you want to, I can respin these patches into two branches, one for dts and
> > one for SoC changes. Probably both branches have to be based on the earlier
> > branch "omap-for-v4.5/81xx-fixes-signed" to avoid merge conflicts though.
>
> Yeah, that sounds good. Please do.
OK updated pull requests sent. It's now three separate pull requests starting
with "[GIT PULL 1/3] reworked fix for earlier ti81xx changes for v4.5 merge
window".
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] omap changes for ti81xx devices and minimal dra62x j5eco-evm support
Date: Tue, 22 Dec 2015 17:47:57 -0800 [thread overview]
Message-ID: <20151223014756.GJ2793@atomide.com> (raw)
In-Reply-To: <CAOesGMjKaRcTHQ40p0pMUW-z1o9HZqEmon3fsFKe46QX82+gDA@mail.gmail.com>
Hi,
* Olof Johansson <olof@lixom.net> [151222 15:41]:
> On Tue, Dec 22, 2015 at 3:33 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Olof Johansson <olof@lixom.net> [151222 14:58]:
> >>
> >> I'm a little puzzled by how you chose to organize this branch. We usually
> >> ask for SoC enablement and new DT files separately. Is there a reason you
> >> couldn't split out the SoC pieces and include those in the soc branch, and
> >> leave the DT contents for this one?
> >
> > Hmm yeah I guess I kept all the 81xx stuff in a single branch because of the
> > earlier largeish set of 81xx fixes that had interlaced dts and SoC changes
> > that had to be in a specific order to keep system booting because of bugs in
> > the dts defined clocks.
> >
> > If you want to, I can respin these patches into two branches, one for dts and
> > one for SoC changes. Probably both branches have to be based on the earlier
> > branch "omap-for-v4.5/81xx-fixes-signed" to avoid merge conflicts though.
>
> Yeah, that sounds good. Please do.
OK updated pull requests sent. It's now three separate pull requests starting
with "[GIT PULL 1/3] reworked fix for earlier ti81xx changes for v4.5 merge
window".
Regards,
Tony
next prev parent reply other threads:[~2015-12-23 1:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 21:06 [GIT PULL 1/4] omap soc changes for v4.5 merge window Tony Lindgren
2015-12-21 21:06 ` [GIT PULL 2/4] omap changes for ti81xx devices and minimal dra62x j5eco-evm support Tony Lindgren
2015-12-21 21:06 ` Tony Lindgren
2015-12-21 21:06 ` [GIT PULL 3/4] omap wakeup-m3 driver for v4.5 merge window Tony Lindgren
2015-12-21 21:06 ` Tony Lindgren
2015-12-21 21:06 ` [GIT PULL 4/4] omap device tree changes for v4.5, part 2 Tony Lindgren
2015-12-21 21:06 ` Tony Lindgren
[not found] ` <567869f7.9440620a.dbdb.65d1SMTPIN_ADDED_BROKEN@mx.google.com>
2015-12-22 22:53 ` [GIT PULL 2/4] omap changes for ti81xx devices and minimal dra62x j5eco-evm support Olof Johansson
2015-12-22 22:53 ` Olof Johansson
2015-12-22 23:33 ` Tony Lindgren
2015-12-22 23:33 ` Tony Lindgren
2015-12-22 23:41 ` Olof Johansson
2015-12-22 23:41 ` Olof Johansson
2015-12-23 1:47 ` Tony Lindgren [this message]
2015-12-23 1:47 ` Tony Lindgren
[not found] ` <567869fb.0295420a.956c9.ffff92e1SMTPIN_ADDED_BROKEN@mx.google.com>
2015-12-22 22:54 ` [GIT PULL 3/4] omap wakeup-m3 driver for v4.5 merge window Olof Johansson
2015-12-22 22:54 ` Olof Johansson
[not found] ` <56786a00.aa93420a.2d595.ffffdbebSMTPIN_ADDED_BROKEN@mx.google.com>
2015-12-22 22:55 ` [GIT PULL 4/4] omap device tree changes for v4.5, part 2 Olof Johansson
2015-12-22 22:55 ` Olof Johansson
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=20151223014756.GJ2793@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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.