linux-kernel - Re: [PATCH v2 0/4] gpiolib: some fixup patches

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: <CAAVeFuLazaZEbbUVtR_Zyub3hgTesW6JcD9Kxgk7dUXuESpLOw@mail.gmail.com>
Date:	Wed, 27 Feb 2013 10:22:24 +0900
From:	Alexandre Courbot <gnurou@...il.com>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Ryan Mallon <rmallon@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"acourbot@...dia.com" <acourbot@...dia.com>
Subject: Re: [PATCH v2 0/4] gpiolib: some fixup patches

On Wed, Feb 27, 2013 at 2:53 AM, Grant Likely <grant.likely@...retlab.ca> wrote:
> On Fri, 22 Feb 2013 11:19:44 +0900, Alexandre Courbot <gnurou@...il.com> wrote:
>> Grant, will you be able to include these for 3.9? They fix code that
>> you merged recently, so I'd be glad if they could be squashed into the
>> patch mentioned in the description.
>
> They won't get squashed in because the tree is already composed and in
> linux-next. I don't rebase unless I really need to. I've applied them
> and I'll probably push to Linus since they are effectively bug fixes of
> a sort and the merge window hasn't closed yet.

That's fine too - as long as the patches with side-effects are merged.
That will allow me to continue going forward with GPIO, thanks!

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