From mboxrd@z Thu Jan 1 00:00:00 1970 From: holler@ahsoftware.de (Alexander Holler) Date: Fri, 21 Mar 2014 09:59:37 +0100 Subject: [PATCH v2] gpio: davinci: fix gpio selection for OF In-Reply-To: References: <5316FFCE.1060603@ti.com> <1394018461-757-1-git-send-email-holler@ahsoftware.de> <5322D529.4070904@ahsoftware.de> <5326F8C5.5090406@ti.com> <532805AE.9000806@ti.com> <532815A8.9090807@ahsoftware.de> Message-ID: <532BFF79.6070906@ahsoftware.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am 21.03.2014 09:28, schrieb Linus Walleij: > On Tue, Mar 18, 2014 at 10:45 AM, Alexander Holler 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? Sure. > It's as simple as sending a mail to Greg once it's upstream. I already though about how to tag every patch I send as Cc: stable, because almost any fix I send either goes through some -next or even -next-next or already is for some stable kernel. (I usually don't even look at -rc kernels, just for some special things I'm waiting for, like this of-gpio for davinci.) Regards, Alexander Holler