From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Greg KH <greg@kroah.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
"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>
Subject: usbip: vhc_hcd: prevent module being removed while device are attached
Date: Wed, 18 Apr 2018 16:43:55 +0000 [thread overview]
Message-ID: <20180418164353.GB2341@sasha-vm> (raw)
On Thu, Apr 05, 2018 at 09:11:02PM +0200, Greg KH wrote:
>On Thu, Apr 05, 2018 at 04:42:46PM +0000, Sasha Levin wrote:
>> Hi.
>>
>> [This is an automated email]
>
>Why are you running this against patches that are not yet in Linus's
>tree? That feels odd. Only about 1/3 of the patches posted end up
>being merged (at best), so don't do extra work by running this on
>patches that might not even be merged at all.
Sorry for late response, this got flagged as spam :/
I was testing out a different approach, that attempts to address the
following issues:
- When we send a review request for a patch, it usually happens weeks
after the patch went upstream. At that point developers have moved
on, and we're less likely to get a helpful response.
- Some patches are tagged for particular stable trees, but don't end up
applying/failing build on them. Usually when you send your rejection
mails for these patches, we see no response. This might mean that
kernels that need a particular bugfix get missed because of things
like trivial dependencies.
- I was planning to integrate a larger set of testing to be done for
these patches both on mainline, and on stable kernels. Like the XFS
example, we could run xfstests for any given patch both on mainline
and on any older stable trees this patch applied to, This would both
help mainline development, and would encourage devs to address any
issues it causes on stable kernels as well.--
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
next reply other threads:[~2018-04-18 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 16:43 Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-05 19:11 usbip: vhc_hcd: prevent module being removed while device are attached Greg KH
2018-04-05 17:09 Sasha Levin
2018-04-05 16:54 Shuah Khan
2018-04-05 16:42 Sasha Levin
2018-04-04 15:14 Shuah Khan
2018-04-04 8:25 Oliver Neukum
2018-04-03 15:56 Shuah Khan
2018-04-03 6:56 Greg Kroah-Hartman
2018-04-02 20:52 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=20180418164353.GB2341@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=greg@kroah.com \
--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 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).