linux-kernel - Re: [PATCH] libata-sff: remove dead code

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] [day] [month] [year] [list]

Message-ID: <1399456806.6659.20.camel@x220>
Date:	Wed, 07 May 2014 12:00:06 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Alan Cox <alan@...ux.intel.com>
Cc:	David Howells <dhowells@...hat.com>, Tejun Heo <tj@...nel.org>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] libata-sff: remove dead code

On Wed, 2014-05-07 at 10:49 +0100, Alan Cox wrote:
> Unless you are editing the config with out of tree changes. Which is
> possible which is why I said ask Dave. It's probably fine but best to be
> safe.

If you mean adding a "config NO_ATA_LEGACY" entry to some Kconfig file,
and setting that symbol during "make *config", that will obviously work.

But if you mean (hand) editing the .config, that wouldn't work, as the
line for CONFIG_NO_ATA_LEGACY would be dropped during "make *config",
wouldn't it?


Paul Bolle

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