From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Brian King <brking@linux.vnet.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"mmc@linux.vnet.ibm.com" <mmc@linux.vnet.ibm.com>,
"brking@pobox.com" <brking@pobox.com>
Subject: Re: [PATCH 0/7] hvcs: Various hvcs device hotplug fixes
Date: Wed, 1 Feb 2023 10:32:08 +0000 [thread overview]
Message-ID: <e705381b-392c-5429-96fa-2543b6f341a1@csgroup.eu> (raw)
In-Reply-To: <20230130224321.164843-1-brking@linux.vnet.ibm.com>
Le 30/01/2023 à 23:43, Brian King a écrit :
> This patch series fixes a number of issues with hotplugging
> hvcs devices including memory leaks as well as, the inability
> to reconnect to a console device after it has been hot added
> back, since it was not getting cleaned up properly on the
> hotplug remove path.
>
> Brian King (7):
> hvcs: Fix hvcs port reference counting
> hvcs: Remove sysfs file prior to vio unregister
> hvcs: Remove sysfs group earlier
> hvcs: Get reference to tty in remove
> hvcs: Use vhangup in hotplug remove
> hvcs: Synchronize hotplug remove with port free
> powerpc: Fix device node refcounting
>
> arch/powerpc/platforms/pseries/reconfig.c | 1 +
> drivers/tty/hvc/hvcs.c | 61 +++++++++--------------
> 2 files changed, 25 insertions(+), 37 deletions(-)
>
As far as I can see, most recent patches in drivers/tty/hvc/ are taken
by Greg Kroah-Hartman <gregkh@linuxfoundation.org> so I'd suggest you
send you series to Greg as he maintains the tty tree.
By the way, does last patch require the 6 previous ones or can it be
applied independently ?
Christophe
next prev parent reply other threads:[~2023-02-01 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 22:43 [PATCH 0/7] hvcs: Various hvcs device hotplug fixes Brian King
2023-01-30 22:43 ` [PATCH 1/7] hvcs: Fix hvcs port reference counting Brian King
2023-01-30 22:43 ` [PATCH 2/7] hvcs: Remove sysfs file prior to vio unregister Brian King
2023-01-30 22:43 ` [PATCH 3/7] hvcs: Remove sysfs group earlier Brian King
2023-01-30 22:43 ` [PATCH 4/7] hvcs: Get reference to tty in remove Brian King
2023-01-30 22:43 ` [PATCH 5/7] hvcs: Use vhangup in hotplug remove Brian King
2023-01-30 22:43 ` [PATCH 6/7] hvcs: Synchronize hotplug remove with port free Brian King
2023-01-30 22:43 ` [PATCH 7/7] powerpc: Fix device node refcounting Brian King
2023-02-01 10:32 ` Christophe Leroy [this message]
2023-02-01 15:09 ` [PATCH 0/7] hvcs: Various hvcs device hotplug fixes 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=e705381b-392c-5429-96fa-2543b6f341a1@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=brking@linux.vnet.ibm.com \
--cc=brking@pobox.com \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).