[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150730110110.GA24546@linux>
Date: Thu, 30 Jul 2015 16:31:10 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rafael Wysocki <rjw@...ysocki.net>,
Chris Metcalf <cmetcalf@...hip.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Joe Perches <joe@...ches.com>, Joerg Roedel <jroedel@...e.de>,
open list <linux-kernel@...r.kernel.org>,
"open list:CPU FREQUENCY DRIVERS" <linux-pm@...r.kernel.org>,
"open list:SUPERH" <linux-sh@...r.kernel.org>,
"Luis R. Rodriguez" <mcgrof@...e.com>,
"open list:NETWORKING DRIVERS" <netdev@...r.kernel.org>,
Nicolas Iooss <nicolas.iooss_linux@....org>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Thomas Gleixner <tglx@...utronix.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>
Subject: Re: [PATCH] bus: subsys: update return type of ->remove_dev() to void
On 30-07-15, 12:59, Borislav Petkov wrote:
> On Thu, Jul 30, 2015 at 03:04:01PM +0530, Viresh Kumar wrote:
> > Its return value is not used by the subsys core and nothing meaningful
> > can be done with it, even if we want to use it. The subsys device is
> > anyway getting removed.
>
> I'm assuming sysfs paths covered by it, will remain intact... ? For the
> microcode loader case that's this hierarchy here:
>
> $ tree /sys/devices/system/cpu/cpu?/microcode/
> /sys/devices/system/cpu/cpu0/microcode/
> ├── processor_flags
> └── version
> /sys/devices/system/cpu/cpu1/microcode/
> ├── processor_flags
> └── version
Yeah, Its not touching the sysfs path at all.
--
viresh
--
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