From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 1/2] part 2 of omap soc changes for v3.19
Date: Fri, 28 Nov 2014 12:22:47 -0800 [thread overview]
Message-ID: <20141128202246.GT2817@atomide.com> (raw)
In-Reply-To: <201411281454.28102.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [141128 05:57]:
> On Sunday 23 November 2014, Tony Lindgren wrote:
> > The following changes since commit 9889278181bcdbae882664d8cee5bb0e064397e4:
> >
> > Merge tag 'for-v3.19/omap-a' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.19/soc (2014-11-14 10:25:12 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.19/hwmod-and-defconfig
> >
> > for you to fetch changes up to 374a735894fe2fb82ba07c6e6b7d326640c1c17f:
> >
> > ARM: omap2plus_defconfig: enable ECAP and EHRPWM (2014-11-21 16:30:28 -0800)
> >
> > ----------------------------------------------------------------
> > SoC related changes for omaps including hwmod clean-up for
> > DSS, and hwmod data for more UARTs and ADC. Also few defconfig
> > changes to enable devices found on am335x and am437x.
>
> Hi Tony,
>
> We have started doing the defconfig changes in a separate branch a while ago.
> I normally don't mess with the tags I got, but this one seemed easy enough
> to redo, as the defconfig changes are all on top.
>
> I ended up pulling in only the commits before the defconfig changes into
> next/soc, and am cherry-picking the defconfig bits onto the next/defconfig
> branch. Hope that's ok for you.
Sure that's fine with me, I only have fixes coming up after the pending
pull requests.
> I checked that the defconfig changes are all harmless and do not depend
> on the other changes, but I may have missed something subtle, so please
> confirm that this is ok for you.
Should be just fine thanks.
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 1/2] part 2 of omap soc changes for v3.19
Date: Fri, 28 Nov 2014 12:22:47 -0800 [thread overview]
Message-ID: <20141128202246.GT2817@atomide.com> (raw)
In-Reply-To: <201411281454.28102.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [141128 05:57]:
> On Sunday 23 November 2014, Tony Lindgren wrote:
> > The following changes since commit 9889278181bcdbae882664d8cee5bb0e064397e4:
> >
> > Merge tag 'for-v3.19/omap-a' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.19/soc (2014-11-14 10:25:12 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.19/hwmod-and-defconfig
> >
> > for you to fetch changes up to 374a735894fe2fb82ba07c6e6b7d326640c1c17f:
> >
> > ARM: omap2plus_defconfig: enable ECAP and EHRPWM (2014-11-21 16:30:28 -0800)
> >
> > ----------------------------------------------------------------
> > SoC related changes for omaps including hwmod clean-up for
> > DSS, and hwmod data for more UARTs and ADC. Also few defconfig
> > changes to enable devices found on am335x and am437x.
>
> Hi Tony,
>
> We have started doing the defconfig changes in a separate branch a while ago.
> I normally don't mess with the tags I got, but this one seemed easy enough
> to redo, as the defconfig changes are all on top.
>
> I ended up pulling in only the commits before the defconfig changes into
> next/soc, and am cherry-picking the defconfig bits onto the next/defconfig
> branch. Hope that's ok for you.
Sure that's fine with me, I only have fixes coming up after the pending
pull requests.
> I checked that the defconfig changes are all harmless and do not depend
> on the other changes, but I may have missed something subtle, so please
> confirm that this is ok for you.
Should be just fine thanks.
Regards,
Tony
next prev parent reply other threads:[~2014-11-28 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 0:44 [GIT PULL 1/2] part 2 of omap soc changes for v3.19 Tony Lindgren
2014-11-23 0:44 ` [GIT PULL 2/2] part 2 of omap dts " Tony Lindgren
2014-11-24 17:09 ` Tony Lindgren
2014-11-24 17:09 ` Tony Lindgren
2014-11-28 13:57 ` Arnd Bergmann
2014-11-28 13:57 ` Arnd Bergmann
2014-11-23 0:44 ` Tony Lindgren
2014-11-23 0:44 ` Tony Lindgren
2014-11-28 13:54 ` [GIT PULL 1/2] part 2 of omap soc " Arnd Bergmann
2014-11-28 13:54 ` Arnd Bergmann
2014-11-28 20:22 ` Tony Lindgren [this message]
2014-11-28 20:22 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2014-11-23 0:44 Tony Lindgren
2014-11-23 0:44 Tony Lindgren
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=20141128202246.GT2817@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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.