From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: remove dmacap,memset from Device tree binding
Date: Mon, 05 Aug 2013 15:12:20 +0200 [thread overview]
Message-ID: <51FFA4B4.5080807@gmail.com> (raw)
In-Reply-To: <20130805122638.GE19280@titan.lakedaemon.net>
On 08/05/13 14:26, Jason Cooper wrote:
> On Mon, Aug 05, 2013 at 10:53:41AM +0100, Mark Rutland wrote:
>> I'm not entirely sure on this. The property described is still true for
>> the device, even if the kernel's not using that information now. My
>> feeling would be to keep them, unless there's a plan to better describe
>> the properties of the XOR channels.
>>
>> It shouldn't harm the kernel to have some properties we don't use at
>> this point in time. If we want to reorganise the binding, the first step
>> would be to make the properties as deprecated, rather than removing them
>> outright.
>
> Ok, that matches what I was originally thinking. The bindings are
> supposed to be OS-agnostic, so the fact that we no longer use it is
> irrelevant. The hardware still has the capability.
>
> Sebastian, I'm just going to drop this patch.
Sure, I am fine with dropping it.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Mark Rutland <mark.rutland@arm.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: remove dmacap,memset from Device tree binding
Date: Mon, 05 Aug 2013 15:12:20 +0200 [thread overview]
Message-ID: <51FFA4B4.5080807@gmail.com> (raw)
In-Reply-To: <20130805122638.GE19280@titan.lakedaemon.net>
On 08/05/13 14:26, Jason Cooper wrote:
> On Mon, Aug 05, 2013 at 10:53:41AM +0100, Mark Rutland wrote:
>> I'm not entirely sure on this. The property described is still true for
>> the device, even if the kernel's not using that information now. My
>> feeling would be to keep them, unless there's a plan to better describe
>> the properties of the XOR channels.
>>
>> It shouldn't harm the kernel to have some properties we don't use at
>> this point in time. If we want to reorganise the binding, the first step
>> would be to make the properties as deprecated, rather than removing them
>> outright.
>
> Ok, that matches what I was originally thinking. The bindings are
> supposed to be OS-agnostic, so the fact that we no longer use it is
> irrelevant. The hardware still has the capability.
>
> Sebastian, I'm just going to drop this patch.
Sure, I am fine with dropping it.
Sebastian
next prev parent reply other threads:[~2013-08-05 13:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:54 [PATCH 0/2] ARM: mvebu: fixes for v3.11 Sebastian Hesselbarth
2013-07-02 10:54 ` Sebastian Hesselbarth
2013-07-02 10:54 ` Sebastian Hesselbarth
2013-07-02 10:54 ` [PATCH 1/2] ARM: remove dmacap,memset from Device tree binding Sebastian Hesselbarth
2013-07-02 10:54 ` Sebastian Hesselbarth
2013-07-02 10:54 ` Sebastian Hesselbarth
2013-07-25 15:31 ` Jason Cooper
2013-07-25 15:31 ` Jason Cooper
2013-08-04 1:09 ` Jason Cooper
2013-08-04 1:09 ` Jason Cooper
2013-08-05 9:53 ` Mark Rutland
2013-08-05 9:53 ` Mark Rutland
2013-08-05 12:26 ` Jason Cooper
2013-08-05 12:26 ` Jason Cooper
2013-08-05 13:12 ` Sebastian Hesselbarth [this message]
2013-08-05 13:12 ` Sebastian Hesselbarth
2013-07-02 10:54 ` [PATCH 2/2] ARM: orion5x: add missing mbus include Sebastian Hesselbarth
2013-07-02 10:54 ` Sebastian Hesselbarth
2013-07-02 10:54 ` Sebastian Hesselbarth
2013-07-25 15:38 ` Jason Cooper
2013-07-25 15:38 ` Jason Cooper
2013-07-25 21:07 ` Jason Cooper
2013-07-25 21:07 ` Jason Cooper
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=51FFA4B4.5080807@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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.