From: Sekhar Nori <nsekhar@ti.com>
To: Alexander Holler <holler@ahsoftware.de>,
Linus Walleij <linus.walleij@linaro.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Prabhakar Lad <prabhakar.csengg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] gpio: davinci: fix gpio selection for OF
Date: Tue, 18 Mar 2014 16:24:17 +0530 [thread overview]
Message-ID: <532825D9.4050708@ti.com> (raw)
In-Reply-To: <532815A8.9090807@ahsoftware.de>
Hi Alexander,
On Tuesday 18 March 2014 03:15 PM, Alexander Holler wrote:
> Am 18.03.2014 09:37, schrieb Sekhar Nori:
>
>> It is safe - at the least it does not break anything that is already
>> working. I guess the decision to put it into -rc depends on whether you
>> consider out of tree dtbs to be a valid usecase for the kernel.
>
> That's all DT is about, getting rid of the necessity for in-tree
> hw-descriptions. ;)
>
> But I don't need any rush here, I'm just unable to understand why the
> -rc phase isn't used for bug fixing as I believe that's what this phase
> is for.
The push back you are seeing is because this is pretty late in -rc
cycle. If this push back was not there the bug fix cycle would probably
never close.
In all probability, if this was -rc2 or even -rc3 there would not be so
much discussion.
Thanks,
Sekhar
next prev parent reply other threads:[~2014-03-18 10:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5315ED51.1000006@ti.com>
2014-03-04 22:06 ` [PATCH] gpio: davinci: fix gpio selection for OF Alexander Holler
2014-03-05 2:27 ` Linus Walleij
2014-03-05 10:43 ` Grygorii Strashko
2014-03-05 11:21 ` [PATCH v2] " Alexander Holler
2014-03-05 13:12 ` Grygorii Strashko
2014-03-11 10:15 ` Linus Walleij
2014-03-14 10:08 ` Alexander Holler
2014-03-14 11:02 ` Linus Walleij
2014-03-14 12:38 ` Alexander Holler
2014-03-14 13:54 ` Linus Walleij
2014-03-14 18:33 ` Alexander Holler
2014-03-14 19:52 ` Linus Walleij
2014-03-15 7:37 ` Alexander Holler
2014-03-17 13:29 ` Sekhar Nori
2014-03-17 14:05 ` Linus Walleij
2014-03-18 8:37 ` Sekhar Nori
2014-03-18 9:45 ` Alexander Holler
2014-03-18 10:54 ` Sekhar Nori [this message]
2014-03-21 8:28 ` Linus Walleij
2014-03-21 8:59 ` Alexander Holler
2014-03-17 14:11 ` Alexander Holler
2014-03-17 14:13 ` Linus Walleij
2014-03-17 15:04 ` Grygorii Strashko
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=532825D9.4050708@ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=holler@ahsoftware.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=robh+dt@kernel.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 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).