linux-kernel - Re: [PATCH 3.13 089/212] ACPI: Remove Kconfig symbol ACPI

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: <1403044874.14743.36.camel@fourier>
Date:	Tue, 17 Jun 2014 15:41:14 -0700
From:	Kamal Mostafa <kamal@...onical.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	kernel-team@...ts.ubuntu.com,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH 3.13 089/212] ACPI: Remove Kconfig symbol ACPI_PROCFS

On Wed, 2014-06-18 at 00:26 +0200, Paul Bolle wrote:
> Kamal,
> 
> On Tue, 2014-06-17 at 14:43 -0700, Kamal Mostafa wrote:
> > 3.13.11.4 -stable review patch.  If anyone has any objections, please let me know.
> > 
> > ------------------
> > 
> > From: Paul Bolle <pebolle@...cali.nl>
> > 
> > commit 7919010c4224e07b871f3b5513d245cc029fcd67 upstream.
> > 
> > Nothing cares about ACPI_PROCFS. This has been the case since v2.6.38.
> > This Kconfig symbol serves no purpose and its help text is now
> > misleading. It can safely be removed. If this symbol would be needed
> > again in the future it can be readded in a commit that adds code that
> > actually uses it.
> > 
> > Signed-off-by: Paul Bolle <pebolle@...cali.nl>
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> > [ kamal: 3.13-stable prereq for
> >   e2a7c3d ACPI: Revert "ACPI: Remove CONFIG_ACPI_PROCFS_POWER and cm_sbsc.c" ]
> 
> I'm curious: how can this patch - which is straightforward cleanup,
> without any further impact - be a prerequisite for a revert, or anything
> else, for that matter?

Hi Paul-

Pulling in this cleanup patch allowed me to cleanly cherry-pick e2a7c3d.
Yes, it would have been possible to massage e2a7c3d into applying but
just cherry-picking both yields a cleaner end result, so that's what I
opted to do for this case.

 -Kamal

> > Signed-off-by: Kamal Mostafa <kamal@...onical.com>
> 
> 
> 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/