linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: holler@ahsoftware.de (Alexander Holler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] gpio: davinci: fix gpio selection for OF
Date: Fri, 21 Mar 2014 09:59:37 +0100	[thread overview]
Message-ID: <532BFF79.6070906@ahsoftware.de> (raw)
In-Reply-To: <CACRpkdZwhP-wMDeNTEq6ELPsYC48xmppzGYTRLSzUewbqhrMvg@mail.gmail.com>

Am 21.03.2014 09:28, schrieb Linus Walleij:
> On Tue, Mar 18, 2014 at 10:45 AM, Alexander Holler <holler@ahsoftware.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?

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

  reply	other threads:[~2014-03-21  8:59 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
2014-03-21  8:28                     ` Linus Walleij
2014-03-21  8:59                       ` Alexander Holler [this message]
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=532BFF79.6070906@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --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 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).