From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: linux-next: Moving mmc tree to kernel.org
Date: Tue, 18 Oct 2016 09:09:44 +1100 [thread overview]
Message-ID: <20161018090944.7cdc0439@canb.auug.org.au> (raw)
In-Reply-To: <CAPDyKFqCvZKzr5fnnKgxc1=3iU+BhhkDkHFv_a01bdxWyAnrHg@mail.gmail.com>
Hi Ulf,
On Mon, 17 Oct 2016 14:51:45 +0200 Ulf Hansson <ulf.hansson@linaro.org> wrote:
>
> I have moved my mmc tree from linaro.org to kernel.org and I would
> appreciate if you could switch to pull my next branch for linux-next
> from there instead.
>
> Old tree:
> git://git.linaro.org/people/ulf.hansson/mmc.git next
>
> New tree
> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git next
Moved from today, thanks. I also renamed the tree from mmc-uh to just
plain mmc.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2016-10-17 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 12:51 linux-next: Moving mmc tree to kernel.org Ulf Hansson
2016-10-17 22:09 ` 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=20161018090944.7cdc0439@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adrian.hunter@intel.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox