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  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]
Date:	Tue, 06 Jan 2015 00:30:56 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	"Zheng, Lv" <lv.zheng@...el.com>
Cc:	Rickard Strandqvist <rickard_strandqvist@...ctrumdigital.se>,
	"Moore, Robert" <robert.moore@...el.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
	Len Brown <lenb@...nel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"devel@...ica.org" <devel@...ica.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] acpi: acpica: utmisc.c:  Remove unused function

On Monday, January 05, 2015 08:32:59 AM Zheng, Lv wrote:
> Hi, Rickard
> 
> > From: Rickard Strandqvist [mailto:rickard_strandqvist@...ctrumdigital.se]
> > Sent: Friday, January 02, 2015 1:16 AM
> > 
> > Remove the function acpi_ut_is_aml_table() that is not used anywhere.
> 
> This function is used by the ACPICA debugger and disassembler.
> The ACPICA release process has just automatically released this function from the ACPICA code base to the Linux kernel.
> 
> We shouldn't just remove it from the Linux kernel code base.
> If we do so, it's just turned into divergences that can hurt the release automation.
> You may use ACPI_FUTURE_USAGE around these functions instead.

Can we do that in upstream ACPICA?


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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