From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: add the omap-pending tree
Date: Fri, 26 Dec 2014 15:40:00 +1100 [thread overview]
Message-ID: <20141226154000.669551a2@canb.auug.org.au> (raw)
In-Reply-To: <20141226153822.20a6bcfe@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Hi Paul,
On Fri, 26 Dec 2014 15:38:22 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Fri, 19 Dec 2014 19:28:08 +0000 (UTC) Paul Walmsley <paul@pwsan.com> wrote:
> >
> > 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.
>
> Added from today (called "omap" and with you as the contact).
Actually called "omap-pending" :-)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-12-26 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 19:28 Paul Walmsley
2014-12-19 20:02 ` Tony Lindgren
2014-12-26 4:46 ` Stephen Rothwell
2014-12-26 4:38 ` Stephen Rothwell
2014-12-26 4:40 ` Stephen Rothwell [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=20141226154000.669551a2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®