From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: anthony.mallet@laas.fr, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] USB: cdc-acm: fix close_delay and closing_wait units in" failed to apply to 4.14-stable tree
Date: Mon, 23 Mar 2020 11:49:34 -0400 [thread overview]
Message-ID: <20200323154934.GT4189@sasha-vm> (raw)
In-Reply-To: <15849665753924@kroah.com>
On Mon, Mar 23, 2020 at 01:29:35PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.14-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 633e2b2ded739a34bd0fb1d8b5b871f7e489ea29 Mon Sep 17 00:00:00 2001
>From: Anthony Mallet <anthony.mallet@laas.fr>
>Date: Thu, 12 Mar 2020 14:31:00 +0100
>Subject: [PATCH] USB: cdc-acm: fix close_delay and closing_wait units in
> TIOCSSERIAL
>
>close_delay and closing_wait are specified in hundredth of a second but stored
>internally in jiffies. Use the jiffies_to_msecs() and msecs_to_jiffies()
>functions to convert from each other.
>
>Signed-off-by: Anthony Mallet <anthony.mallet@laas.fr>
>Cc: stable <stable@vger.kernel.org>
>Link: https://lore.kernel.org/r/20200312133101.7096-1-anthony.mallet@laas.fr
>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Both this and b401f8c4f492 ("USB: cdc-acm: fix rounding error in
TIOCSSERIAL") depended on b401f8c4f492 ("USB: cdc-acm: fix rounding
error in TIOCSSERIAL").
I've fixed it to remove the dependency and queued both patches to
4.19-4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-03-23 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 12:29 FAILED: patch "[PATCH] USB: cdc-acm: fix close_delay and closing_wait units in" failed to apply to 4.14-stable tree gregkh
2020-03-23 15:49 ` Sasha Levin [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=20200323154934.GT4189@sasha-vm \
--to=sashal@kernel.org \
--cc=anthony.mallet@laas.fr \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.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).