From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>,
linux-can <linux-can@vger.kernel.org>
Subject: Re: r8a7795 dtsi file in can-next
Date: Mon, 29 Feb 2016 13:07:16 +0100 [thread overview]
Message-ID: <56D43474.7070405@pengutronix.de> (raw)
In-Reply-To: <SG2PR06MB1038D3EF38013CAA39BAD598C3BA0@SG2PR06MB1038.apcprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
On 02/29/2016 12:25 PM, Ramesh Shanmugasundaram wrote:
> Any reasons why arch/arm64/boot/dts/renesas/r8a7795.dtsi is not up to
> date with linux-next in tag:linux-can-next-for-4.6-20160226? When I
> submit my patch set, should I ignore the dtsi changes?
My upstream is David Miller's net-next/master. So you can either wait
until the dtsi changes will end up there or submit your dtsi changes via
another tree.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
parent reply other threads:[~2016-02-29 12:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <SG2PR06MB1038D3EF38013CAA39BAD598C3BA0@SG2PR06MB1038.apcprd06.prod.outlook.com>]
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=56D43474.7070405@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=ramesh.shanmugasundaram@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).