linux-kernel - Re: linux-next: add the omap-pending tree

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: <20141219200230.GJ23854@atomide.com>
Date:	Fri, 19 Dec 2014 12:02:30 -0800
From:	Tony Lindgren <tony@...mide.com>
To:	Paul Walmsley <paul@...an.com>
Cc:	sfr@...b.auug.org.au, linux-omap@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: add the omap-pending tree

* Paul Walmsley <paul@...an.com> [141219 11:30]:
> 
> Hi Stephen,
> 
> Might you be willing to include this branch in your linux-next builds?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git#for-next
> 
> It will include OMAP clock, bus architecture, and low-level power 
> management patches that are planned to be included in pull requests to the 
> OMAP upstream maintainer, Tony Lindgren.  He in turn will submit pull 
> requests to the arm-soc tree.  The objective in including this branch is 
> to get these patches integration-tested earlier than they would be 
> otherwise.

Makes sense to me. The delay in getting omap stuff into Linux next
via arm-soc for-next is just too long because of the large number
of pending pull requests for various ARM SoCs.

While at it, can you please also (re-)add omap for-next too:

git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git#for-next

Regards,

Tony
--
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/