From: "Stefan (metze) Metzmacher" <metze@samba.org>
To: Greg KH <gregkh@suse.de>
Cc: David Miller <davem@davemloft.net>,
oliver@neukum.name, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usbnet/cdc_ncm: add missing .reset_resume hook
Date: Tue, 07 Jun 2011 19:07:58 +0200 [thread overview]
Message-ID: <4DEE5AEE.8070901@samba.org> (raw)
In-Reply-To: <20110607144348.GB19246@suse.de>
[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]
Am 07.06.2011 16:43, schrieb Greg KH:
> On Tue, Jun 07, 2011 at 09:38:12AM +0200, Stefan (metze) Metzmacher wrote:
>> Am 06.06.2011 17:06, schrieb Greg KH:
>>> On Mon, Jun 06, 2011 at 02:23:16PM +0200, Stefan (metze) Metzmacher wrote:
>>>> Hi David,
>>>>
>>>>> From: Stefan Metzmacher <metze@samba.org>
>>>>> Date: Wed, 1 Jun 2011 14:01:41 +0200
>>>>>
>>>>>> This avoids messages like this after suspend:
>>>>>>
>>>>>> cdc_ncm 2-1.4:1.6: no reset_resume for driver cdc_ncm?
>>>>>> cdc_ncm 2-1.4:1.7: no reset_resume for driver cdc_ncm?
>>>>>> cdc_ncm 2-1.4:1.6: usb0: unregister 'cdc_ncm' usb-0000:00:1d.0-1.4, CDC NCM
>>>>>>
>>>>>> This is important for the Ericsson F5521gw GSM/UMTS modem.
>>>>>> Otherwise modemmanager looses the fact that the cdc_ncm and cdc_acm devices
>>>>>> belong together.
>>>>>>
>>>>>> The cdc_ether module does the same.
>>>>>>
>>>>>> Signed-off-by: Stefan Metzmacher <metze@samba.org>
>>>>>
>>>>> Applied and queued up for -stable, thanks.
>>>>
>>>> It seems to be part of 3.0-rc2, but I'm not seeing it in any stable tree
>>>> yet...
>>>>
>>>> When can I expect it in stable trees like 2.6.38.y?
>>>
>>> The .38.y tree is closed and will not have new releases, so you will
>>> never see it there, sorry.
>>
>> Ok, are there chances for .39.y?
>
> There are, it requires the patch to be in Linus's tree first,
It's already there:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=85e3c65fa3a1d0542c181510a950a2be7733ff29
> please see Documentation/stable_kernel_rules.txt for the details.
Thanks for the pointer. It seems I've missed the Cc: <stable@kernel.org>
line(s).
Would this be the correct syntax in order to get it into 2.6.38.x and
2.6.39.x?
(2.6.38 wasn't closed at the time I submitted the patch)
Cc: <stable@kernel.org> # .38.x
Cc: <stable@kernel.org> # .39.x
Should I resubmit the patch, or can you just cherry pick
85e3c65fa3a1d0542c181510a950a2be7733ff29
from Linus's tree?
metze
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-06-07 17:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 9:13 cdc_ncm: device gets unregistered on resume Stefan Metzmacher
2011-06-01 9:13 ` [PATCH] usbnet/cdc_ncm: add missing .reset_resume hook Stefan Metzmacher
2011-06-01 9:43 ` Oliver Neukum
2011-06-01 10:03 ` Stefan (metze) Metzmacher
2011-06-01 10:08 ` Alexey ORISHKO
2011-06-01 12:01 ` Stefan Metzmacher
2011-06-01 12:01 ` Stefan Metzmacher
2011-06-02 4:11 ` David Miller
2011-06-06 12:23 ` Stefan (metze) Metzmacher
2011-06-06 15:06 ` Greg KH
2011-06-07 7:38 ` Stefan (metze) Metzmacher
2011-06-07 14:43 ` Greg KH
2011-06-07 17:07 ` Stefan (metze) Metzmacher [this message]
2011-06-07 17:35 ` Greg KH
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=4DEE5AEE.8070901@samba.org \
--to=metze@samba.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.name \
/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).