From: Scott Wood <scottwood@freescale.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@lists.ozlabs.org, galak@kernel.crashing.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-next@vger.kernel.org
Subject: linux-next: add scottwood/linux.git
Date: Fri, 9 May 2014 16:15:33 -0500 [thread overview]
Message-ID: <1399670133.15726.440.camel@snotra.buserror.net> (raw)
In-Reply-To: <1395709794.12479.411.camel@snotra.buserror.net>
On Mon, 2014-03-24 at 20:09 -0500, Scott Wood wrote:
> On Mon, 2014-03-24 at 10:33 +1100, Benjamin Herrenschmidt wrote:
> > On Mon, 2014-03-24 at 10:16 +1100, Benjamin Herrenschmidt wrote:
> > > On Wed, 2014-03-19 at 23:25 -0500, Scott Wood wrote:
> > > > The following changes since commit c7e64b9ce04aa2e3fad7396d92b5cb92056d16ac:
> > > >
> > > > powerpc/powernv Platform dump interface (2014-03-07 16:19:10 +1100)
> > > >
> > > > are available in the git repository at:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/scottwood/linux.git next
> > > >
> > > > for you to fetch changes up to 48b16180d0d91324e5d2423c6d53d97bbe3dcc14:
> > > >
> > > > fsl/pci: The new pci suspend/resume implementation (2014-03-19 22:37:44 -0500)
> > >
> > > Stephen just informed me that your tree wasn't in -next ... Kumar's
> > > still is.
> > >
> > > Can you guys fix that up ? I somewhat rely on the FSL stuff to simmer
> > > in -next on its own.
>
> Stephen, what's the process for adding a tree?
ping
-Scott
>
> I suppose we should update MAINTAINERS while we're at it.
>
> > Oh and where is my little summary to put in the merge commit ?
> >
> > I made one up for this time around.
>
> Oops, forgot again. Now I've added something to the script I use to
> generate pull requests, to give me a reminder.
>
> -Scott
>
next parent reply other threads:[~2014-05-09 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140320042527.GA23206@home.buserror.net>
[not found] ` <1395616617.3460.109.camel@pasglop>
[not found] ` <1395617608.3460.113.camel@pasglop>
[not found] ` <1395709794.12479.411.camel@snotra.buserror.net>
2014-05-09 21:15 ` Scott Wood [this message]
2014-05-11 22:23 ` linux-next: add scottwood/linux.git Stephen Rothwell
2014-05-12 0:19 ` 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=1399670133.15726.440.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox