From: Jean Delvare <khali@linux-fr.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Marek Vasut <marex@denx.de>,
Linus Walleij <linus.walleij@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Samuel Ortiz <samuel@sortiz.org>
Subject: Re: [git pull] GPIO for v3.10
Date: Fri, 3 May 2013 23:22:42 +0200 [thread overview]
Message-ID: <20130503232242.5a0978ea@endymion.delvare> (raw)
In-Reply-To: <CA+55aFx4Q6tSidW2sihZSjNyRYJLftT=s8QKpx6bCe_4M0hwug@mail.gmail.com>
On Fri, 3 May 2013 09:56:09 -0700, Linus Torvalds wrote:
> On Fri, May 3, 2013 at 9:51 AM, Jean Delvare <khali@linux-fr.org> wrote:
> >
> > The real problem here is that two patches which depended on each other
> > went to you through 2 different maintainer trees (mfd maintained by
> > Samuel Ortiz and gpio maintained by Grant L. & Linus W.), and the git
> > pull requests reached you in the wrong order. That doesn't make us all
> > irresponsible and lame contributors/maintainers, does it?
>
> F*ck yes it does.
>
> It means that NOBODY EVEN TEST-COMPILED THE TREE THAT GOT SENT TO ME.
>
> WTF?
It means that nobody test-compiled that tree with CONFIG_GPIO_UCB1400=m.
> If that's not "irresponsible and lame", I don't know what the hell is.
Hell, n. 1. The place or state of punishment of the wicked after
death. 2. A world where people volunteering to maintain kernel
subsystems get fewer, because they received more blame for their casual
mistakes than praise for their thankless work.
--
Jean Delvare
next prev parent reply other threads:[~2013-05-03 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 10:37 Grant Likely
2013-05-03 16:14 ` Linus Torvalds
2013-05-03 16:51 ` Jean Delvare
2013-05-03 16:55 ` Grant Likely
2013-05-03 16:56 ` Linus Torvalds
2013-05-03 21:22 ` Jean Delvare [this message]
2013-05-03 21:48 ` Linus Torvalds
2013-05-06 11:03 ` Grant Likely
2013-05-03 17:17 ` Grant Likely
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=20130503232242.5a0978ea@endymion.delvare \
--to=khali@linux-fr.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=samuel@sortiz.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®