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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 1 Jan 2012 14:32:48 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Stephen Warren <swarren@...dia.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: Pass name instead of device to pin_config_*

On Mon, Dec 19, 2011 at 7:20 PM, Stephen Warren <swarren@...dia.com> wrote:
> Linus Walleij wrote at Sunday, December 18, 2011 3:27 PM:
>>
>> I had to fix it up a bit to match the other
>> refactoring patch I made so check the result in my tree or -next.
>
> Yes, I think that looks fine, thanks.
>
> Thanks for fixing up the documentation for me too.
>
> BTW, do you know which commits you're planning on you're planning on
> sending to mainline during the next merge window? If it includes these
> two patches,

Yes, everything that has landed in -next will be sent upstream,
including this.

> I may be able to convert Tegra over to using the new pinctrl
> driver in 3.3. And is your for-next branch stable (i.e. never rebased)
> so that the arm-soc tree can use it as a dependency for my patches?

It is rebased infrequently, and never this late in the -rc series.
I may add fixes on top though.

The for-next branch is basically a subset of devel excluding
any controversial stuff, so up to a certain point, then I keep
the under discussion stuff on top of for-next.

Thanks,
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/

Powered by blists - more mailing lists