From: "Steinar H. Gunderson" <sesse@google.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
linux-mm@kvack.org,
Kernel development list <linux-kernel@vger.kernel.org>,
David Laight <David.Laight@ACULAB.COM>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Does vm_operations_struct require a .owner field?
Date: Wed, 6 Jan 2016 00:54:21 +0100 [thread overview]
Message-ID: <20160105235418.GA1599@imap.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1601051619200.1350-100000@iolanthe.rowland.org>
On Tue, Jan 05, 2016 at 04:31:09PM -0500, Alan Stern wrote:
> Thank you. So it looks like I was worried about nothing.
>
> Steinar, you can remove the try_module_get/module_put lines from your
> patch. Also, the list_del() and comment in usbdev_release() aren't
> needed -- at that point we know the memory_list has to be empty since
> there can't be any outstanding URBs or VMA references. If you take
> those things out then the patch should be ready for merging.
Good, thanks. Did so, compiled, testing it still works, sending :-)
/* Steinar */
--
Software Engineer, Google Switzerland
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-01-05 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.1601051024110.1666-100000@iolanthe.rowland.org>
2016-01-05 16:27 ` Does vm_operations_struct require a .owner field? Alan Stern
2016-01-05 20:58 ` Kirill A. Shutemov
2016-01-05 21:31 ` Alan Stern
2016-01-05 23:54 ` Steinar H. Gunderson [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=20160105235418.GA1599@imap.gmail.com \
--to=sesse@google.com \
--cc=David.Laight@ACULAB.COM \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).