All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brandt <Chris.Brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
To: Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>,
	Ulf Hansson <ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Wolfram Sang
	<wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>,
	Geert Uytterhoeven
	<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux-Renesas
	<linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: [PATCH v6 0/3] mmc: sh_mobile_sdhi: fix missing r7s72100 clocks
Date: Thu, 26 Jan 2017 12:53:10 +0000	[thread overview]
Message-ID: <SG2PR06MB1165AEC165D52358154B5EE38A770@SG2PR06MB1165.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20170126103013.GB27721-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>

Hi Simon,

On Thursday, January 26, 2017, Simon Horman wrote:
> > Thanks, applied patch1 and patch2 for next. Patch3 is for Simon, I
> > guess!? (And I can add Rob's ack afterwards).
> 
> Thanks, I will take care of the 3rd patch.
> 
> Chris, is it safe to apply the 3rd patch without the first 2 patches
> present?

Yes, it is safe.

Chris

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Simon Horman <horms@verge.net.au>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH v6 0/3] mmc: sh_mobile_sdhi: fix missing r7s72100 clocks
Date: Thu, 26 Jan 2017 12:53:10 +0000	[thread overview]
Message-ID: <SG2PR06MB1165AEC165D52358154B5EE38A770@SG2PR06MB1165.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20170126103013.GB27721@verge.net.au>

Hi Simon,

On Thursday, January 26, 2017, Simon Horman wrote:
> > Thanks, applied patch1 and patch2 for next. Patch3 is for Simon, I
> > guess!? (And I can add Rob's ack afterwards).
> 
> Thanks, I will take care of the 3rd patch.
> 
> Chris, is it safe to apply the 3rd patch without the first 2 patches
> present?

Yes, it is safe.

Chris


  parent reply	other threads:[~2017-01-26 12:53 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 20:28 [PATCH v6 0/3] mmc: sh_mobile_sdhi: fix missing r7s72100 clocks Chris Brandt
2017-01-25 20:28 ` [PATCH v6 1/3] mmc: sh_mobile_sdhi: add support for 2 clocks Chris Brandt
2017-01-25 20:28 ` [PATCH v6 2/3] mmc: sh_mobile_sdhi: explain clock bindings Chris Brandt
     [not found]   ` <20170125202810.16876-3-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-01-30 20:37     ` Rob Herring
2017-01-30 20:37       ` Rob Herring
2017-01-25 20:28 ` [PATCH v6 3/3] ARM: dts: r7s72100: update sdhi " Chris Brandt
     [not found] ` <20170125202810.16876-1-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-01-26  8:07   ` [PATCH v6 0/3] mmc: sh_mobile_sdhi: fix missing r7s72100 clocks Ulf Hansson
2017-01-26  8:07     ` Ulf Hansson
2017-01-26 10:12     ` Wolfram Sang
2017-01-26 12:53       ` Chris Brandt
2017-01-27  8:40       ` Simon Horman
2017-01-27  8:40         ` Simon Horman
2017-01-27 14:57       ` Ulf Hansson
2017-01-26 10:30     ` Simon Horman
     [not found]       ` <20170126103013.GB27721-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-01-26 12:53         ` Chris Brandt [this message]
2017-01-26 12:53           ` Chris Brandt
2017-01-26 14:53 [PATCH 0/4] arm64: renesas: enable M3ULCB board peripherals Vladimir Barinov
2017-01-26 14:54 ` [PATCH 1/4] arm64: dts: m3ulcb: enable I2C Vladimir Barinov
2017-02-01 12:35   ` Geert Uytterhoeven
2017-01-26 14:54 ` [PATCH 2/4] arm64: dts: m3ulcb: Update memory node to 2 GiB map Vladimir Barinov
2017-02-01 12:38   ` Geert Uytterhoeven
2017-02-02 18:19   ` Geert Uytterhoeven
2017-02-02 18:21     ` Vladimir Barinov
2017-01-26 14:54 ` [PATCH 3/4] arm64: dts: m3ulcb: enable EthernetAVB Vladimir Barinov
2017-02-01 13:10   ` Geert Uytterhoeven
2017-01-26 14:54 ` [PATCH 4/4] arm64: dts: m3ulcb: enable HS200 for eMMC Vladimir Barinov
     [not found] ` <1485442422-18259-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-03-17 22:02   ` [PATCH 0/4] arm64: renesas: enable M3ULCB board peripherals Sjoerd Simons
2017-03-17 22:02     ` Sjoerd Simons
     [not found]     ` <1489788135.8957.2.camel-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2017-04-06  9:53       ` Geert Uytterhoeven
2017-04-06  9:53         ` Geert Uytterhoeven
2017-04-07 13:52         ` Simon Horman
     [not found]           ` <20170407135212.GA24096-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-04-08 13:18             ` Simon Horman
2017-04-08 13:18               ` Simon Horman
2017-04-18  1:01           ` Simon Horman
2017-01-26 15:13 [PATCH 0/2] arm64: renesas: enable H3ULCB " Vladimir Barinov
2017-01-26 15:13 ` Vladimir Barinov
     [not found] ` <1485443606-22566-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-01-26 15:13   ` [PATCH 1/2] arm64: dts: h3ulcb: Update memory node to 4 GiB map Vladimir Barinov
2017-01-26 15:13     ` Vladimir Barinov
2017-02-01 12:40     ` Geert Uytterhoeven
2017-02-02  9:18       ` Simon Horman
     [not found]     ` <1485443632-22612-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
     [not found]       ` <1485442486-18427-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
     [not found]         ` <1485442469-18378-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
     [not found]           ` <1485442460-18339-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
     [not found]             ` <1485442449-18300-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-02-01 13:05         ` [PATCH 4/4] arm64: dts: m3ulcb: enable HS200 for eMMC Geert Uytterhoeven
2017-02-01 13:05           ` Geert Uytterhoeven
2017-01-26 15:14 ` [PATCH 2/2] arm64: dts: h3ulcb: " Vladimir Barinov
2017-01-27  8:29   ` Simon Horman
2017-02-01 13:05   ` Geert Uytterhoeven

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=SG2PR06MB1165AEC165D52358154B5EE38A770@SG2PR06MB1165.apcprd06.prod.outlook.com \
    --to=chris.brandt-zm6kxycvzfbbdgjk7y7tuq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
    --cc=horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
    --cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.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.