From: Greg KH <gregkh@linuxfoundation.org>
To: xinhui <xinhui.pan@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiri Slaby <jslaby@suse.com>,
yanmin_zhang@linux.intel.com, alan@linux.intel.com
Subject: Re: [PATCH V2 RESEND] tty/n_gsm.c: use gsm->num to remove mux itself from gsm_mux[]
Date: Wed, 31 Aug 2016 16:01:38 +0200 [thread overview]
Message-ID: <20160831140138.GA13669@kroah.com> (raw)
In-Reply-To: <57874F5F.5050000@linux.vnet.ibm.com>
On Thu, Jul 14, 2016 at 04:37:51PM +0800, xinhui wrote:
> From: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
>
> There is one filed gsm->num to store mux's index of gsm_mux[]. So use
> gsm->num to remove itself from gsm_mux[] instead of the for-loop
> traverse in gsm_cleanup_mux().
>
> Signed-off-by: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
> Reviewed-by: Alan Cox <alan@linux.intel.com>
> ---
> change from V1:
> lock is also held for the if()
> ---
> drivers/tty/n_gsm.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
Doesn't apply to my tree :(
prev parent reply other threads:[~2016-08-31 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 8:37 xinhui
2016-08-31 14:01 ` Greg KH [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=20160831140138.GA13669@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xinhui.pan@linux.vnet.ibm.com \
--cc=yanmin_zhang@linux.intel.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
Powered by JetHome