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 17:46:59 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Grant Likely <grant.likely@...retlab.ca>
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 Tue, Feb 02, 2010 at 01:31:18AM -0700, Grant Likely wrote:
> On Tue, Feb 2, 2010 at 1:21 AM, Paul Mundt <lethal@...ux-sh.org> wrote:
> > On Tue, Feb 02, 2010 at 01:17:49AM -0700, Grant Likely wrote:
> >> 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).
> >>
> > If there's someone actively looking after the SPI stuff then that's fine.
> 
> I am now.  There wasn't anyone for a while.
> 
> > I didn't bother bouncing this one off of the SPI list since it's a
> > hardware-specific correctness fix and has no dependency on anything
> > subsystem related.
> 
> Fair enough, but the patch itself came across the SPI list, and so it
> showed up in the patchwork tracking of spi-devel-general which I'm
> using to keep on top of everything.  I brief reply to the patch email
> would have let me know that I didn't have to waste any time with it.
> 
Ahh.. this is where the confusion came from. The initial version of the
patch was only posted to the sh list, Magnus asked for it to be reposted
to the spi list and I hadn't heard anything about it since then, so I
assumed the poster just disappeared and I just cleaned it up and applied
it by hand. Apparently it was reposted but the sh list was dropped, so I
never saw the updated version. If I had known that it had hit the SPI
list I would have followed up there, I'll be more careful next time now
that I know someone is paying attention :-)
--
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/