From: Stephen Warren <swarren@wwwdotorg.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
Pawel Moll <pawel.moll@arm.com>, Lee Jones <lee@kernel.org>,
linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Eric Anholt <eric@anholt.net>, Rob Herring <robh+dt@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] DT: bindings: remove bcm2835-sdhci
Date: Fri, 17 Jun 2016 12:59:36 -0600 [thread overview]
Message-ID: <57644898.60402@wwwdotorg.org> (raw)
In-Reply-To: <1995060523.43076.c268f06d-da3c-427e-800f-fbc65895c323.open-xchange@email.1und1.de>
On 06/09/2016 12:11 PM, Stefan Wahren wrote:
> Hi Stephen,
>
>> Stephen Warren <swarren@wwwdotorg.org> hat am 3. Juni 2016 um 22:00
>> geschrieben:
>>
>>
>> On 06/03/2016 01:47 PM, Stefan Wahren wrote:
>>> The sdhci-iproc also supports bcm2835. So this binding is obsolete.
>>
>> sdhci-iproc supports this binding, so I don't believe the binding is
>> obsolete. The duplicate implementations (drivers) can possibly be
>> removed, but not the binding doc, which is (or at least could be) still
>> in use.
>
> sorry for my late reply.
>
> So the brcm,bcm2835-sdhci.txt must be kept, even if the compatible string
> "brcm,bcm2835-sdhci" has been added to brcm,sdhci-iproc.txt?
Sorry for the slow reply; I was on vacation.
So, if the binding documentation has been collapsed into the other
binding document, then it's OK to remove this one. I took a look at the
iproc binding doc and it looks completely compatible with this removed
binding doc, so I think this patch is OK.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] DT: bindings: remove bcm2835-sdhci
Date: Fri, 17 Jun 2016 12:59:36 -0600 [thread overview]
Message-ID: <57644898.60402@wwwdotorg.org> (raw)
In-Reply-To: <1995060523.43076.c268f06d-da3c-427e-800f-fbc65895c323.open-xchange@email.1und1.de>
On 06/09/2016 12:11 PM, Stefan Wahren wrote:
> Hi Stephen,
>
>> Stephen Warren <swarren@wwwdotorg.org> hat am 3. Juni 2016 um 22:00
>> geschrieben:
>>
>>
>> On 06/03/2016 01:47 PM, Stefan Wahren wrote:
>>> The sdhci-iproc also supports bcm2835. So this binding is obsolete.
>>
>> sdhci-iproc supports this binding, so I don't believe the binding is
>> obsolete. The duplicate implementations (drivers) can possibly be
>> removed, but not the binding doc, which is (or at least could be) still
>> in use.
>
> sorry for my late reply.
>
> So the brcm,bcm2835-sdhci.txt must be kept, even if the compatible string
> "brcm,bcm2835-sdhci" has been added to brcm,sdhci-iproc.txt?
Sorry for the slow reply; I was on vacation.
So, if the binding documentation has been collapsed into the other
binding document, then it's OK to remove this one. I took a look at the
iproc binding doc and it looks completely compatible with this removed
binding doc, so I think this patch is OK.
next prev parent reply other threads:[~2016-06-17 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 19:47 [PATCH 0/2] mmc: remove sdhci-bcm2835 Stefan Wahren
2016-06-03 19:47 ` Stefan Wahren
2016-06-03 19:47 ` [PATCH 1/2] DT: bindings: remove bcm2835-sdhci Stefan Wahren
2016-06-03 19:47 ` Stefan Wahren
[not found] ` <1464983233-27001-2-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2016-06-03 20:00 ` Stephen Warren
2016-06-03 20:00 ` Stephen Warren
2016-06-09 18:11 ` Stefan Wahren
2016-06-09 18:11 ` Stefan Wahren
2016-06-17 18:59 ` Stephen Warren [this message]
2016-06-17 18:59 ` Stephen Warren
2016-06-03 19:47 ` [PATCH 2/2] mmc: sdhci-bcm2835: remove driver Stefan Wahren
2016-06-03 19:47 ` Stefan Wahren
2016-06-04 0:02 ` Eric Anholt
2016-06-04 0:02 ` Eric Anholt
2016-06-22 15:22 ` [PATCH 0/2] mmc: remove sdhci-bcm2835 Ulf Hansson
2016-06-22 15:22 ` Ulf Hansson
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=57644898.60402@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=ulf.hansson@linaro.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.