[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwFkXM5ZoVJfetX5puYzc8efXQKzYpjYcxjBM2J_iPohQ@mail.gmail.com>
Date: Tue, 21 Jul 2015 15:29:03 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Subject: Re: [GIT PULL] pin control fixes for the v4.2 series, take one
On Tue, Jul 21, 2015 at 2:25 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
>
> Ah, how could I miss that. Selective vision or something.
> Well let's see if Linus (the big penguin) want to fix it up, I
> can for one live with it.
Not the first time it has happened, and fixing it up generally is more
pain than it's worth.
We have worse examples of nasty crap. See for example commit
c6d409cfd0fd. That was supposed to be a "cleanup".
Oh well.
Mistakes happen. I don't get upset about occasionally screwed up
commit logs. If it becomes a _pattern_, now that is when I might start
getting annoyed.
Linus
--
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