linux-kernel - Re: [PATCH 10/30] Use menuconfig objects

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: <Pine.LNX.4.61.0704111024090.32056@yvahk01.tjqt.qr>
Date:	Wed, 11 Apr 2007 10:32:01 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Jean Delvare <khali@...ux-fr.org>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	i2c@...sensors.org
Subject: Re: [PATCH 10/30] Use menuconfig objects - I2C

Hi Jean,


On Apr 11 2007 10:14, Jean Delvare wrote:
>On Tue, 10 Apr 2007 23:11:41 +0200 (MEST), Jan Engelhardt wrote:
>> 
>> Use menuconfigs instead of menus, so the whole menu can be disabled at        
>> once instead of going through all options.
>> 
>> Signed-off-by: Jan Engelhardt <jengelh@....de>
>
>The patch looks OK to me, except that it needs to be adjusted for the
>current state of the i2c subsystem. This kind of patch should be built
>on top on Andrew Morton's latest tree, not Linus Torvalds'.
>
>What is the merge plan?

If it applies with not too many rejects, take it and fixup
potentially new config options.
Else
  If Andrew's latest is a tarball or some sort of file (it is),
  I can redo it (with a big grumpy face ;-)
  Else
    You have to do it.

I think that's the typical way of doing things.
Documentation/SubmittingPatches only mandates latest kernel version 
(which most likely means Linus's tree), I could rebase.

Thanks,
Jan
-- 
-
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/