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, 14 Mar 2014 19:33:12 +0100	[thread overview]
Message-ID: <53234B68.5090300@ahsoftware.de> (raw)
In-Reply-To: <CACRpkdZscprsy7kyqHPUMEMYJ_TKgG2bYR7mdrG4hTDp1w1nDg@mail.gmail.com>

Am 14.03.2014 14:54, schrieb Linus Walleij:
> On Fri, Mar 14, 2014 at 1:38 PM, Alexander Holler <holler@ahsoftware.de> wrote:
>
>>> In that case it is hardly a fix that we need to rush out to the entire
>>> world.
>>
>> And I thought the reason for -rc is actually to fix bugs. But I never
>> understood the magical ways and timings patches make their way into
>> mainline. ;)
>
> OK so it works like this: early in the -rc cycle we fix any bugs, documentation
> or whatever. At this point it's *regressions* so the fix need to fix something
> that broke in the merge window (or an earlier merge window).

Sorry, but I don't believe that. It's always time to fix regressions and 
bugs.

> If it is a new feature that never worked in the first place I would
> not call that
> a regression. There are no existing users out there that can experience
> regressions from a previously working system.

I believe that no (stable) kernel should introduce new known bugs (if 
fixes are available) and I wouldn't make a difference if it's a new 
feature or not. Usually people don't care if something is new or not if 
it has bugs

Anyway, I'm just curious and try to understand, I have a fix. ;)

Regards,

Alexander Holler

  reply	other threads:[~2014-03-14 18:33 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 [this message]
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
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=53234B68.5090300@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).