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: <4E9D05FB.4080607@snapgear.com>
Date:	Tue, 18 Oct 2011 14:52:11 +1000
From:	Greg Ungerer <gerg@...pgear.com>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	<linux-m68k@...ts.linux-m68k.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 12/21] m68k: drop unused Kconfig symbols

Hi Paul,

On 17/10/11 17:52, Paul Bolle wrote:
> On Mon, 2011-10-17 at 10:50 +1000, Greg Ungerer wrote:
>> I have no problem with the changes. But it will clash with the
>> reworking of the Kconfig files currently sitting in linux-next
>> for merging in the 3.2 merge window.
>
> So should I put this on hold and see what's needed after those reworked
> Kconfig files are merged in mainline? Or would you prefer to have that
> done beforehand (ie, I'll try to redo this on top of current linux-next
> and get the redone patch in linux-next before the 3.2 merge)?

I won't be too difficult for you to redo your patch. If you can do it
on top of linux-next real soon I can push it into my m68knommu git
tree for-next branch. But it would need to be very soon :-)

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@...pgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ