linux-kernel - Re: [PATCH-next] drivers/hwmon: remove new _

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]

Date:	Fri, 10 Jan 2014 08:22:26 -0800
From:	Guenter Roeck <linux@...ck-us.net>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Fenghua Yu <fenghua.yu@...el.com>,
	Jean Delvare <khali@...ux-fr.org>, lm-sensors@...sensors.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH-next] drivers/hwmon: remove new __cpuinit usage from
 coretemp.c

On Fri, Jan 10, 2014 at 10:10:23AM -0500, Paul Gortmaker wrote:
> Commit da9e8c7a7b99b245c464ff45c7bde38a4b510019 ("hwmon: (coretemp)
> Use PCI host bridge ID to identify CPU if necessary") added a new
> instance of the __cpuinit macro usage.
> 
> We removed this a couple versions ago; we now want to remove
> the compat no-op stubs.  Introducing new users is not what
> we want to see at this point in time, as it will break once
> the stubs are gone.
> 
> Cc: Guenter Roeck <linux@...ck-us.net>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
> ---
> 
> [Patch based on today's linux-next tree, so if hwmon next content
>  gets rebased, then the above commit ID will be invalidated; if it
>  _does_ get rebased, then feel free to squash this fix into the orig.]
> 
Hi Paul,

thanks a lot for the fix. I rebased hwmon-next and removed __cpuinitconst from
the original commit, so the problem should be gone in the next iteration of
linux-next.

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