All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Simon Horman <horms@verge.net.au>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] ARM: shmobile: r7s72100: Enable L2 cache
Date: Mon, 6 Feb 2017 14:13:09 +0000	[thread overview]
Message-ID: <SG2PR06MB1165ABE474EDB227522FCF148A400@SG2PR06MB1165.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20170206082525.GB13441@verge.net.au>

Hi Simon,

On Monday, February 06, 2017, Simon Horman wrote:
> is it possible to apply the .dtsi and .c portions of this change
> separately and still get sane behaviour at each step?
> 
> If so I would like to request that this patch be split into two patches,
> one for .c and one for .dtsi. This will allow me to apply the patches to
> separate branches which will in turn make it easier for me to get the
> change accepted.

OK, no problem.

I tried thinking about which way you guys would want it...I had a 50/50
shot...I picked the wrong one ;)


Chris

  reply	other threads:[~2017-02-06 14:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 21:20 [PATCH] ARM: shmobile: r7s72100: Enable L2 cache Chris Brandt
2017-02-06  8:25 ` Simon Horman
2017-02-06 14:13   ` Chris Brandt [this message]
2017-02-06  8:50 ` Geert Uytterhoeven
2017-02-06  8:50   ` Geert Uytterhoeven
2017-02-06  8:50   ` Geert Uytterhoeven
2017-02-06 14:58   ` Chris Brandt
2017-02-06 14:58     ` Chris Brandt
2017-02-06 15:30     ` Geert Uytterhoeven
2017-02-06 15:30       ` Geert Uytterhoeven
2017-02-06 16:02       ` Chris Brandt
2017-02-06 16:02         ` Chris Brandt

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=SG2PR06MB1165ABE474EDB227522FCF148A400@SG2PR06MB1165.apcprd06.prod.outlook.com \
    --to=chris.brandt@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.