From: Greg KH <gregkh@linuxfoundation.org>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, brking@pobox.com,
mmc@linux.vnet.ibm.com, linux-serial@vger.kernel.org
Subject: Re: [PATCH 2/6] hvcs: Remove sysfs file prior to vio unregister
Date: Wed, 1 Feb 2023 21:05:07 +0100 [thread overview]
Message-ID: <Y9rF81tIiFioCvpE@kroah.com> (raw)
In-Reply-To: <20230201195743.303163-3-brking@linux.vnet.ibm.com>
On Wed, Feb 01, 2023 at 01:57:39PM -0600, Brian King wrote:
> This moves the removal of the rescan sysfs attribute to occur
> before the call to unregister the vio to ensure the removal
> does not fail due to the vio driver already being freed.
>
> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
> ---
> drivers/tty/hvc/hvcs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/hvc/hvcs.c b/drivers/tty/hvc/hvcs.c
> index faf5ccfc561e..9131dcb2e8d8 100644
> --- a/drivers/tty/hvc/hvcs.c
> +++ b/drivers/tty/hvc/hvcs.c
> @@ -1519,6 +1519,8 @@ static int __init hvcs_module_init(void)
>
> static void __exit hvcs_module_exit(void)
> {
> + driver_remove_file(&hvcs_vio_driver.driver, &driver_attr_rescan);
Again, set the default group for the driver and then you don't have to
do any of this at all please.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-01 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 19:57 [PATCH 0/6] hvcs: Various hvcs device hotplug fixes Brian King
2023-02-01 19:57 ` [PATCH 1/6] hvcs: Fix hvcs port reference counting Brian King
2023-02-01 19:57 ` [PATCH 2/6] hvcs: Remove sysfs file prior to vio unregister Brian King
2023-02-01 20:05 ` Greg KH [this message]
2023-02-01 19:57 ` [PATCH 3/6] hvcs: Remove sysfs group earlier Brian King
2023-02-01 20:04 ` Greg KH
2023-02-01 19:57 ` [PATCH 4/6] hvcs: Get reference to tty in remove Brian King
2023-02-01 19:57 ` [PATCH 5/6] hvcs: Use vhangup in hotplug remove Brian King
2023-02-01 19:57 ` [PATCH 6/6] hvcs: Synchronize hotplug remove with port free Brian King
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=Y9rF81tIiFioCvpE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=brking@linux.vnet.ibm.com \
--cc=brking@pobox.com \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmc@linux.vnet.ibm.com \
/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