linux-kernel - Re: [GIT PULL] sh updates for 2.6.33-rc7

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:	Tue, 2 Feb 2010 01:17:49 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Paul Mundt <lethal@...ux-sh.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org,
	spi-devel-general@...ts.sourceforge.net
Subject: Re: [GIT PULL] sh updates for 2.6.33-rc7

On Mon, Feb 1, 2010 at 9:06 PM, Paul Mundt <lethal@...ux-sh.org> wrote:
> Please pull from:
>
>        master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git sh/for-2.6.33
>
> Which contains:
>
> Magnus Damm (1):
>      usb: r8a66597-hdc disable interrupts fix
>
> Marek Skuczynski (2):
>      sh: Fix access to released memory in dwarf_unwinder_cleanup()
>      sh: Fix access to released memory in clk_debugfs_register_one()
>
> Markus Pietrek (1):
>      spi: spi_sh_msiof: Fixed data sampling on the correct edge

Hold the phone; please coordinate with me before picking up SPI
patches into your tree.  I don't mind arch specific spi changes going
in via a different tree, but I'd like to know about it before I waste
time farting around with the same patch (like I did with this one
tonight, and only found out that you also picked it up when I came
across this pull request by chance).

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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/