linux-kernel - Re: [PATCH 00/20] Blackfin update for 2.6.22-rc3

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: <alpine.LFD.0.98.0705291356290.26602@woody.linux-foundation.org>
Date:	Tue, 29 May 2007 13:59:55 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bryan Wu <bryan.wu@...log.com>
cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/20] Blackfin update for 2.6.22-rc3



On Mon, 28 May 2007, Bryan Wu wrote:
> 
>  - Blackfin arch update including BF54x initial supporting
>  - Blackfin driver update: serial/spi/rtc
>  - Provide new Blackfin watchdog driver
>  - binfmt_flat.c for Blackfin arch modification

I realize that this all just touches blackfin-specific stuff, but after 
-rc3 I really prefer not to bother with these things..

Also, for stuff that is really just an architecture that I can't even 
test, and where there is a clear maintainership thing, I'd actually prefer 
to just do a git merge, if possible. It's not like I will likely start 
looking at some blackfin-specific patches. Judging from the diffs, you do 
actually use git, do you have a place where you could export these kinds 
of patch-series as a git tree instead?

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