devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: dbaryshkov@gmail.com, dwmw2@infradead.org,
	santosh.shilimkar@ti.com, arnd@arndb.de, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	grant.likely@linaro.org, devicetree@vger.kernel.org,
	grygorii.strashko@ti.com, linux@arm.linux.org.uk,
	sergei.shtylyov@cogentembedded.com, linux-doc@vger.kernel.org,
	w-kwok2@ti.com, rdunlap@infradead.org, sboyd@codeaurora.org,
	linux-kernel@vger.kernel.org, m-karicheri2@ti.com,
	olof@lixom.net, linux-arm-kernel@lists.infradead.org
Subject: Re: [Patch v5 3/7] mfd: ti-keystone-devctrl: add bindings for device state control
Date: Thu, 22 May 2014 19:30:23 +0300	[thread overview]
Message-ID: <537E261F.10401@ti.com> (raw)
In-Reply-To: <537E224E.3060601@ti.com>


On 05/22/2014 07:14 PM, Ivan Khoronzhuk wrote:
>
> On 05/22/2014 06:33 PM, Lee Jones wrote:
>>>> Why do I only have this patch?  Where is the rest of the set?  Also,
>>>> it's on v5 and I don't recall seeing the other 4 versions?
>>> It's strange I've sent whole series on
>>>
>>> linux-kernel@vger.kernel.org
>>> linux-arm-kernel@lists.infradead.org
>>> linux-doc@vger.kernel.org
>>> devicetree@vger.kernel.org
>>>
>>> v4 is also was sent to lists in question:
>>> https://lkml.org/lkml/2014/5/21/359
>> But did you send them to me?  I don't parse the list.
>>
>
> Sorry.
> Becouse /scripts/get_maintainer.pl  patches/reset_driver_v6/* hadn't 
> been listed you
> It's because there is no patch with "code" for the bindings you've 
> comment.
>
> I should check it by hand for mtd.
>
> The bindings for mtd device_state_control were added only on v5
> And it's added only to describe what is the node we've used in a 
> keystone DT.
> The node is planned to be used only via syscon phandle, there is no 
> driver for it,
> and compatible string for "ti,keystone-devctrl" added only to be 
> matched by
> a high-level device driver if needed.
>
> I'll send new v6 series to you also.
> Once again sorry.
>

s/mtd/mfd

-- 
Regards,
Ivan Khoronzhuk


  reply	other threads:[~2014-05-22 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 13:48 [Patch v5 0/7] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 1/7] power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Ivan Khoronzhuk
2014-05-22 14:14   ` Lee Jones
2014-05-22 14:32     ` Ivan Khoronzhuk
2014-05-22 15:33       ` Lee Jones
2014-05-22 16:14         ` Ivan Khoronzhuk
2014-05-22 16:30           ` Ivan Khoronzhuk [this message]
2014-05-22 13:48 ` [Patch v5 4/7] power: reset: add bindings for keystone reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 5/7] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
     [not found] ` <1400766516-14537-1-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2014-05-22 13:48   ` [Patch v5 6/7] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 7/7] ARM: keystone: enable reset driver support Ivan Khoronzhuk
2014-05-22 13:52 ` [Patch v5 0/7] Introduce keystone reset driver Santosh Shilimkar
2014-05-22 13:54   ` Arnd Bergmann
2014-05-22 13:58     ` Ivan Khoronzhuk
2014-05-22 14:02     ` Santosh Shilimkar

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=537E261F.10401@ti.com \
    --to=ivan.khoronzhuk@ti.com \
    --cc=arnd@arndb.de \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=grygorii.strashko@ti.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=m-karicheri2@ti.com \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=sboyd@codeaurora.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=w-kwok2@ti.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).