From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: "valentina.manea.m@gmail.com" <valentina.manea.m@gmail.com>,
"shuah@kernel.org" <shuah@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: usbip: vhc_hcd: prevent module being removed while device are attached
Date: Thu, 5 Apr 2018 17:09:12 +0000 [thread overview]
Message-ID: <20180405170910.GO7561@sasha-vm> (raw)
On Thu, Apr 05, 2018 at 10:54:59AM -0600, Shuah Khan wrote:
>On 04/05/2018 10:42 AM, Sasha Levin wrote:
>> Hi.
>>
>> [This is an automated email]
>>
>> This commit has been processed by the -stable helper bot and determined
>> to be a high probability candidate for -stable trees. (score: 13.1846)
>>
>> The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
>>
>> v4.15.15: Build OK!
>> v4.14.32: Build OK!
>> v4.9.92: Failed to apply! Possible dependencies:
>> 3920ad4951e2 ("usbip: vhc_hcd: prevent module being removed while device are attached">
>> v4.4.126: Failed to apply! Possible dependencies:
>> 0775a9cbc694 ("usbip: vhci extension: modifications to vhci driver")
>> 3920ad4951e2 ("usbip: vhc_hcd: prevent module being removed while device are attached")
>
>This patch will not go into Linus's tree. Please don't pull it into stables.
Commits indeed won't be picked up unless they make it to Linus' tree
(per the -stable rules). I'll clarify that in future mails, thank you!--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: "valentina.manea.m@gmail.com" <valentina.manea.m@gmail.com>,
"shuah@kernel.org" <shuah@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] usbip: vhc_hcd: prevent module being removed while device are attached
Date: Thu, 5 Apr 2018 17:09:12 +0000 [thread overview]
Message-ID: <20180405170910.GO7561@sasha-vm> (raw)
In-Reply-To: <dcfe9644-25c3-d317-d467-140906f93d87@osg.samsung.com>
On Thu, Apr 05, 2018 at 10:54:59AM -0600, Shuah Khan wrote:
>On 04/05/2018 10:42 AM, Sasha Levin wrote:
>> Hi.
>>
>> [This is an automated email]
>>
>> This commit has been processed by the -stable helper bot and determined
>> to be a high probability candidate for -stable trees. (score: 13.1846)
>>
>> The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
>>
>> v4.15.15: Build OK!
>> v4.14.32: Build OK!
>> v4.9.92: Failed to apply! Possible dependencies:
>> 3920ad4951e2 ("usbip: vhc_hcd: prevent module being removed while device are attached">
>> v4.4.126: Failed to apply! Possible dependencies:
>> 0775a9cbc694 ("usbip: vhci extension: modifications to vhci driver")
>> 3920ad4951e2 ("usbip: vhc_hcd: prevent module being removed while device are attached")
>
>This patch will not go into Linus's tree. Please don't pull it into stables.
Commits indeed won't be picked up unless they make it to Linus' tree
(per the -stable rules). I'll clarify that in future mails, thank you!
next reply other threads:[~2018-04-05 17:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 17:09 Sasha Levin [this message]
2018-04-05 17:09 ` [PATCH] usbip: vhc_hcd: prevent module being removed while device are attached Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2018-04-18 16:43 Sasha Levin
2018-04-18 16:43 ` [PATCH] " Sasha Levin
2018-04-05 19:11 Greg KH
2018-04-05 19:11 ` [PATCH] " Greg KH
2018-04-05 16:54 Shuah Khan
2018-04-05 16:54 ` [PATCH] " Shuah Khan
2018-04-05 16:50 usbip: vhci_hcd: Fix usb device and sockfd leaks Shuah Khan
2018-04-05 16:50 ` [PATCH] " Shuah Khan
2018-04-05 16:42 usbip: vhc_hcd: prevent module being removed while device are attached Sasha Levin
2018-04-05 16:42 ` [PATCH] " Sasha Levin
2018-04-05 16:42 usbip: vhci_hcd: Fix usb device and sockfd leaks Sasha Levin
2018-04-05 16:42 ` [PATCH] " Sasha Levin
2018-04-04 15:14 usbip: vhc_hcd: prevent module being removed while device are attached Shuah Khan
2018-04-04 15:14 ` [PATCH] " Shuah Khan
2018-04-04 8:25 Oliver Neukum
2018-04-04 8:25 ` [PATCH] " Oliver Neukum
2018-04-03 15:56 Shuah Khan
2018-04-03 15:56 ` [PATCH] " Shuah Khan
2018-04-03 13:54 usbip: vhci_hcd: Fix usb device and sockfd leaks Shuah Khan
2018-04-03 13:54 ` [PATCH] " Shuah Khan
2018-04-03 6:56 Greg Kroah-Hartman
2018-04-03 6:56 ` [PATCH] " Greg KH
2018-04-03 6:56 usbip: vhc_hcd: prevent module being removed while device are attached Greg Kroah-Hartman
2018-04-03 6:56 ` [PATCH] " Greg KH
2018-04-02 20:52 usbip: vhci_hcd: Fix usb device and sockfd leaks Shuah Khan
2018-04-02 20:52 ` [PATCH] " Shuah Khan
2018-04-02 20:52 usbip: vhc_hcd: prevent module being removed while device are attached Shuah Khan
2018-04-02 20:52 ` [PATCH] " Shuah Khan
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=20180405170910.GO7561@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=stable@vger.kernel.org \
--cc=valentina.manea.m@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.