linux-kernel - Re: [PATCH 3/4] OMAP: Define TCA6424 max number of possible IRQs

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>] [day] [month] [year] [list]

Message-ID: <CACRpkdaPCf7eo5V3pHvVE=JFuZp=otXjvQ1US1bHXQ7D1QbDeQ@mail.gmail.com>
Date:	Sat, 14 Jul 2012 22:44:59 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	"Mahapatra, Chandrabhanu" <cmahapatra@...com>
Cc:	Tony Lindgren <tony@...mide.com>, grant.likely@...retlab.ca,
	linus.walleij@...ricsson.com, rob.herring@...xeda.com,
	linux-kernel@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	leed.aguilar@...com
Subject: Re: [PATCH 3/4] OMAP: Define TCA6424 max number of possible IRQs

On Thu, Jul 12, 2012 at 3:00 PM, Mahapatra, Chandrabhanu
<cmahapatra@...com> wrote:

> OK, but if your taking this patch through GPIO tree the better if the 4th
> patch is taken through it. TCA6424 fails if both the patches are not
> present.

If the situation is such they should be squashed into one since the
point after the first before the second patch is not bisectable.

Yours,
Linus Walleij
--
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/