From: Scott Branden <sbranden@broadcom.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robherring2@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kevin Cernekee <cernekee@gmail.com>
Subject: Re: linux-next: manual merge of the dt-rh tree with the mips tree
Date: Fri, 27 Mar 2015 04:56:58 +0000 [thread overview]
Message-ID: <C0EDB62B-3B1F-49D9-9E9F-75101B978339@broadcom.com> (raw)
In-Reply-To: <20150327152536.23f0a8b8@canb.auug.org.au>
Rob,
Apologies that the mips tree is deleting files that I was synchronizing names on. Would you like me to provide new patch that doesn't touch files that mips tree is now deleting?
Scott
> On Mar 26, 2015, at 9:26 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> <mime-attachment>
next prev parent reply other threads:[~2015-03-27 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 4:25 linux-next: manual merge of the dt-rh tree with the mips tree Stephen Rothwell
2015-03-27 4:56 ` Scott Branden [this message]
2015-03-27 5:00 ` Rob Herring
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=C0EDB62B-3B1F-49D9-9E9F-75101B978339@broadcom.com \
--to=sbranden@broadcom.com \
--cc=cernekee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=robherring2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox