Re: Central Linux ARM wiki
On Mon, Apr 8, 2013 at 2:04 PM, Luis R. Rodriguez wrote: > Do we have a central place to centrally document ARM development > upstream? I'd like to start using a central place to start documenting > things for some stuff I'd like to work on and I don't want to use any > vendor specific stuff. Are we go happy with using elinux.org ? If so > can we add a reference to that as the place for ARM development from > wiki.kernel.org ? I haven't heard any complaints, so Konstantin, can we refer elinux.org from wiki.kernel.org as the wiki for ARM development ? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Central Linux ARM wiki
Do we have a central place to centrally document ARM development upstream? I'd like to start using a central place to start documenting things for some stuff I'd like to work on and I don't want to use any vendor specific stuff. Are we go happy with using elinux.org ? If so can we add a reference to that as the place for ARM development from wiki.kernel.org ? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 00/15] change default_llseek action
On Wed, Sep 15, 2010 at 2:39 AM, Stephen Rothwell wrote: > Hi Arnd, > > On Tue, 14 Sep 2010 22:22:28 +0200 Arnd Bergmann wrote: >> >> Stephen, please add >> git+ssh://master.kernel.org/pub/scm/linux/kernel/git/arnd/bkl.git llseek > > Added from today. > > Thanks for adding your subsystem tree as a participant of linux-next. As > you may know, this is not a judgment of your code. The purpose of > linux-next is for integration testing and to lower the impact of > conflicts between subsystems in the next merge window. > > You will need to ensure that the patches/commits in your tree/series have > been: > * submitted under GPL v2 (or later) and include the Contributor's > Signed-off-by, I should note this should say the code should be GPL-compatible, it doesn't need to be GPLv2 (or later). Furthermore the contributors of the subsystem respect the individual licenses of the files through the Developers Certificate of Origin, which tells the developers what the meaning of Signed-off-by means. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
