linux-kernel - Re: Blackfin.git tree change

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]

Date:	Sun, 13 Nov 2011 22:50:41 +0800
From:	Bob Liu <lliubbo@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linux-Kernel <linux-kernel@...r.kernel.org>,
	linux-next@...r.kernel.org, Mike Frysinger <vapier@...too.org>,
	sonic.zhang@...log.com
Subject: Re: Blackfin.git tree change

Hi, Stephen

On Sun, Nov 13, 2011 at 8:19 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Bob,
>
> On Fri, 11 Nov 2011 18:49:59 +0800 Bob Liu <lliubbo@...il.com> wrote:
>>
>> I'll take most of the arch Blackfin maintain work from now on.
>>
>> My tree is:
>> git://git.kernel.org/pub/scm/linux/kernel/git/lliubbo/blackfin.git#for-linus
>>
>> Would you please update it for linux-next.
>
> OK, I have switched to that tree and will put you as the contact.  Should
> I also keep Mike as a contact for problems with this tree?
>

Yes, Please.

> The only thing I did notice, is that this commit was in Mike's tree but
> is not in yours:
>
> Author: Sonic Zhang <sonic.zhang@...log.com>
> Date:   Mon Aug 1 17:53:21 2011 +0800
>
>    Blackfin: add serial TX IRQ in individual platform resource
>
>    The serial TX IRQ is not simply (RX IRQ + 1) on some Blackfin chips,
>    so move the values to the platform resources.
>
>    Signed-off-by: Sonic Zhang <sonic.zhang@...log.com>
>    Signed-off-by: Mike Frysinger <vapier@...too.org>
>
> Just in case it was forgotten.
>

Sorry for that, I thought that patch has been merged to mainline.
I'll update it soon. Thanks.

> 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,
>     * posted to the relevant mailing list,
>     * reviewed by you (or another maintainer of your subsystem tree),
>     * successfully unit tested, and
>     * destined for the current or next Linux merge window.
>
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.
>
> --
> Cheers,
> Stephen Rothwell
> sfr@...b.auug.org.au
>
> Legal Stuff:
> By participating in linux-next, your subsystem tree contributions are
> public and will be included in the linux-next trees.  You may be sent
> e-mail messages indicating errors or other issues when the
> patches/commits from your subsystem tree are merged and tested in
> linux-next.  These messages may also be cross-posted to the linux-next
> mailing list, the linux-kernel mailing list, etc.  The linux-next tree
> project and IBM (my employer) make no warranties regarding the linux-next
> project, the testing procedures, the results, the e-mails, etc.  If you
> don't agree to these ground rules, let me know and I'll remove your tree
> from participation in linux-next.
>

-- 
Regards,
--Bob
--
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/