From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: sfr@canb.auug.org.au, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: add the omap-pending tree
Date: Fri, 19 Dec 2014 12:02:30 -0800 [thread overview]
Message-ID: <20141219200230.GJ23854@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1412191715230.3102@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [141219 11:30]:
>
> Hi Stephen,
>
> Might you be willing to include this branch in your linux-next builds?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git#for-next
>
> It will include OMAP clock, bus architecture, and low-level power
> management patches that are planned to be included in pull requests to the
> OMAP upstream maintainer, Tony Lindgren. He in turn will submit pull
> requests to the arm-soc tree. The objective in including this branch is
> to get these patches integration-tested earlier than they would be
> otherwise.
Makes sense to me. The delay in getting omap stuff into Linux next
via arm-soc for-next is just too long because of the large number
of pending pull requests for various ARM SoCs.
While at it, can you please also (re-)add omap for-next too:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git#for-next
Regards,
Tony
next prev parent reply other threads:[~2014-12-19 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 19:28 linux-next: add the omap-pending tree Paul Walmsley
2014-12-19 20:02 ` Tony Lindgren [this message]
2014-12-26 4:46 ` Stephen Rothwell
2014-12-26 4:38 ` Stephen Rothwell
2014-12-26 4:40 ` Stephen Rothwell
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=20141219200230.GJ23854@atomide.com \
--to=tony@atomide.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sfr@canb.auug.org.au \
/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.