From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 5/5] ARM: remove #gpio-ranges-cells property
Date: Mon, 15 Jul 2013 17:02:29 -0600 [thread overview]
Message-ID: <51E47F85.4050905@wwwdotorg.org> (raw)
In-Reply-To: <51E44ED9.9020807@gmail.com>
On 07/15/2013 01:34 PM, Rob Herring wrote:
> On 07/15/2013 01:40 PM, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> This property is no longer required by the GPIO binding. Remove it.
>
> Won't this break compatibility with older kernel? It is one thing to
> deprecate, but removal is another. If the relevant maintainers don't
> care, then I guess it is fine.
Yes.
I had originally hoped this could sneak in late for 3.11, but I suppose
it's too late now. vf610.dtsi is a new file in 3.11 so has no legacy to
protect.
Admittedly, the #gpio-cells property was added into the SPEAr files in 3.10.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Shiraz Hashim <shiraz.hashim-qxv4g6HH51o@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Haojian Zhuang
<haojian.zhuang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Jingchang Lu <b35083-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH V2 5/5] ARM: remove #gpio-ranges-cells property
Date: Mon, 15 Jul 2013 17:02:29 -0600 [thread overview]
Message-ID: <51E47F85.4050905@wwwdotorg.org> (raw)
In-Reply-To: <51E44ED9.9020807-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 07/15/2013 01:34 PM, Rob Herring wrote:
> On 07/15/2013 01:40 PM, Stephen Warren wrote:
>> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>
>> This property is no longer required by the GPIO binding. Remove it.
>
> Won't this break compatibility with older kernel? It is one thing to
> deprecate, but removal is another. If the relevant maintainers don't
> care, then I guess it is fine.
Yes.
I had originally hoped this could sneak in late for 3.11, but I suppose
it's too late now. vf610.dtsi is a new file in 3.11 so has no legacy to
protect.
Admittedly, the #gpio-cells property was added into the SPEAr files in 3.10.
next prev parent reply other threads:[~2013-07-15 23:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 18:40 [PATCH V2 1/5] gpio: clean up gpio-ranges documentation Stephen Warren
2013-07-15 18:40 ` Stephen Warren
2013-07-15 18:40 ` [PATCH V2 2/5] of: move documentation of of_parse_phandle_with_args Stephen Warren
2013-07-15 18:40 ` Stephen Warren
2013-07-15 18:40 ` [PATCH V2 3/5] of: introduce of_parse_phandle_with_fixed_args Stephen Warren
2013-07-15 18:40 ` Stephen Warren
2013-07-15 18:59 ` Sergei Shtylyov
2013-07-15 18:59 ` Sergei Shtylyov
2013-07-15 23:06 ` Stephen Warren
2013-07-15 23:06 ` Stephen Warren
2013-07-15 18:40 ` [PATCH V2 4/5] gpio: implement gpio-ranges binding document fix Stephen Warren
2013-07-15 18:40 ` Stephen Warren
2013-07-15 18:40 ` [PATCH V2 5/5] ARM: remove #gpio-ranges-cells property Stephen Warren
2013-07-15 18:40 ` Stephen Warren
2013-07-15 19:34 ` Rob Herring
2013-07-15 19:34 ` Rob Herring
2013-07-15 23:02 ` Stephen Warren [this message]
2013-07-15 23:02 ` Stephen Warren
2013-07-16 23:30 ` Stephen Warren
2013-07-16 23:30 ` Stephen Warren
2013-07-17 1:50 ` Rob Herring
2013-07-17 1:50 ` Rob Herring
2013-07-17 2:58 ` Stephen Warren
2013-07-17 2:58 ` Stephen Warren
2013-07-18 1:35 ` Laurent Pinchart
2013-07-18 1:35 ` Laurent Pinchart
2013-07-22 22:31 ` [PATCH V2 1/5] gpio: clean up gpio-ranges documentation Linus Walleij
2013-07-22 22:31 ` Linus Walleij
2013-07-23 16:14 ` Stephen Warren
2013-07-23 16:14 ` Stephen Warren
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=51E47F85.4050905@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.