linux-kernel - Re: [git pull] GPIO for v3.10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACxGe6sG6DQKTXDXmb71VRTaHWaUXBc3Zs=-wHwNWVEX44e3ow@mail.gmail.com>
Date:	Fri, 3 May 2013 17:55:14 +0100
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Marek Vasut <marex@...x.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Samuel Ortiz <samuel@...tiz.org>
Subject: Re: [git pull] GPIO for v3.10

On Fri, May 3, 2013 at 5:51 PM, Jean Delvare <khali@...ux-fr.org> wrote:
> Hi Linus,
>
> On Fri, 3 May 2013 09:14:44 -0700, Linus Torvalds 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?

Actually, it does make us (me) wrong and irresponsible. It should
never have happened because dependencies should never be committed to
different trees.

g.
--
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/