| 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
| ||
|
Date: Tue, 10 Apr 2012 13:02:35 -0600 From: Stephen Warren <swarren@...dotorg.org> To: Linus Walleij <linus.walleij@...aro.org> CC: linux-kernel@...r.kernel.org Subject: Re: [PATCH V4 REPOST 5/5] pinctrl: tegra: Add complete device tree support On 04/10/2012 12:31 PM, Linus Walleij wrote: > On Tue, Apr 10, 2012 at 5:55 PM, Stephen Warren <swarren@...dotorg.org> wrote: > >> Is your pinctrl for-next branch considered "stable" (i.e. it won't ever >> be rebased) at least up to commit a57be23 "pinctrl: tegra: Add complete >> device tree support"? > > Not quite yet, because I would expect the occasional -rc fix for > -rc3 or so. Hmm. Adding extra fixes wouldn't require you to rebase your branch would it, just add extra changes on top of it? >> If so, I'll use it as a base for the Tegra GPIO and pinmux rework branch. > > Soon-ish that'd work... Well, I guess I can base my branch on top of your current branch in order to include the Tegra changes in linux-next. Once pinctrl is stable, I can rebase on your stable commit and make sure I don't send any pull requests until that's happened. I'd really like to allow other people to pick up all the Tegra GPIO and pinmux rework without having to work on top of my personal repo rather than linux-next. -- 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