linux-kernel - Re: [GIT PULL] m32r: Cleanup linker script

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.DEB.1.10.0909230021320.15822@dr-wily.mit.edu>
Date:	Wed, 23 Sep 2009 09:46:37 -0400 (EDT)
From:	Tim Abbott <tabbott@...lice.com>
To:	Hirokazu Takata <takata@...ux-m32r.org>
cc:	torvalds@...ux-foundation.org, linux-m32r@...linux-m32r.org,
	linux-kernel@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>
Subject: Re: [GIT PULL] m32r: Cleanup linker script

On Wed, 23 Sep 2009, Hirokazu Takata wrote:

> Hi, Linus,
> 
> Sorry, there was a cross in the post.
> 
> I was not conscious of Sam's acknowledgement mail.  And a newer patchset
> has been sent by Tim Abbott on Sep. 22, 2009 - 10:23:21 EST.
> 
> > [PATCH 00/13] Linker script cleanup patches for various architectures
> 
> The newer patchset includes updates for not only m32r but also
> parisc, xtenza, h8300, mn10300 and um.
> 
> What do I deal with such a cross architectural patchset?

Sorry for the miscommunication.

My patchset is just 5 orthogonal patchsets included together; there's no 
dependence between the various architectures.  These were just the subset 
of the architecture linker script cleanups that were ready to be merged at 
that time.

The 6 m32r patches I sent to Linus are exactly the same as what's in your 
pull request, so it doesn't matter which one gets merged.

	-Tim Abbott
--
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/