From: Viresh Kumar <viresh.kumar@linaro.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
Chris Metcalf <cmetcalf@ezchip.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Joe Perches <joe@perches.com>, Joerg Roedel <jroedel@suse.de>,
open list <linux-kernel@vger.kernel.org>,
"open list:CPU FREQUENCY DRIVERS" <linux-pm@vger.kernel.org>,
"open list:SUPERH" <linux-sh@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
Nicolas Iooss <nicolas.iooss_linux@m4x.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Thomas Gleixner <tglx@linutronix.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>
Subject: Re: [PATCH] bus: subsys: update return type of ->remove_dev() to void
Date: Thu, 30 Jul 2015 16:31:10 +0530 [thread overview]
Message-ID: <20150730110110.GA24546@linux> (raw)
In-Reply-To: <20150730105917.GA25460@nazgul.tnic>
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
prev parent reply other threads:[~2015-07-30 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 9:34 [PATCH] bus: subsys: update return type of ->remove_dev() to void Viresh Kumar
2015-07-30 10:59 ` Borislav Petkov
2015-07-30 11:01 ` Viresh Kumar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150730110110.GA24546@linux \
--to=viresh.kumar@linaro.org \
--cc=bp@alien8.de \
--cc=cmetcalf@ezchip.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.iooss_linux@m4x.org \
--cc=paul.gortmaker@windriver.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).