From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 6
Date: Fri, 6 Nov 2015 13:45:46 +0100 [thread overview]
Message-ID: <563CA0FA.1060306@de.ibm.com> (raw)
In-Reply-To: <20151106142410.0f016358@canb.auug.org.au>
Am 06.11.2015 um 04:24 schrieb Stephen Rothwell:
> Merging access_once/linux-next (fc7f9754db6c s390/dma: Allow per device dma ops)
Stephen,
can you rename that branch to borntraeger/linux-next ?
It used to carry the access_once reworks, but it will in general hold things
that I work on.
Thanks?
Christian
next prev parent reply other threads:[~2015-11-06 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 3:24 linux-next: Tree for Nov 6 Stephen Rothwell
2015-11-06 12:45 ` Christian Borntraeger [this message]
2015-11-09 21:31 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2023-11-06 0:47 Stephen Rothwell
2021-11-06 2:58 Stephen Rothwell
2020-11-06 6:18 Stephen Rothwell
2019-11-06 8:03 Stephen Rothwell
2018-11-06 3:14 Stephen Rothwell
2017-11-06 7:30 Stephen Rothwell
2014-11-06 8:43 Stephen Rothwell
2013-11-06 9:28 Stephen Rothwell
2012-11-06 5:48 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=563CA0FA.1060306@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).