[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZwhP-wMDeNTEq6ELPsYC48xmppzGYTRLSzUewbqhrMvg@mail.gmail.com>
Date: Fri, 21 Mar 2014 09:28:16 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Alexander Holler <holler@...oftware.de>
Cc: Sekhar Nori <nsekhar@...com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"davinci-linux-open-source@...ux.davincidsp.com"
<davinci-linux-open-source@...ux.davincidsp.com>,
Grygorii Strashko <grygorii.strashko@...com>,
Alexandre Courbot <gnurou@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Prabhakar Lad <prabhakar.csengg@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Grant Likely <grant.likely@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] gpio: davinci: fix gpio selection for OF
On Tue, Mar 18, 2014 at 10:45 AM, Alexander Holler <holler@...oftware.de> wrote:
> 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.
Right now it is mostly a practical issue to me, as I applied the patch to
the devel (for-next) branch, then committed new development on top of
it.
If I send it for fixes now the same patch will come in two ways as I
really do not like to rebase my tree at this point.
So I'd prefer to keep this for next and then have it tagged for stable as
v3.14 is released, if that is OK?
It's as simple as sending a mail to Greg once it's upstream.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists