From: Jan Dumon <j.dumon-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] hso: fix for the 'invalid frame length' messages
Date: Thu, 02 Apr 2009 10:34:02 +0200 [thread overview]
Message-ID: <49D4787A.6060808@option.com> (raw)
In-Reply-To: <20090402.012032.67869929.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
David Miller wrote:
> From: Jan Dumon <j.dumon-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>
> Date: Mon, 30 Mar 2009 11:44:59 +0200
>
>> Some devices cannot send very short usb transfers. To get around this the
>> firmware adds a known pattern and flags the driver that it should check for
>> this pattern on short transfers. This flag was not taken into account by
>> the driver.
>>
>> Signed-off-by: Jan Dumon <j.dumon-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>
>
> These patches do not apply cleanly, please respin them against the
> current sources.
The diff was taken against 2.6.29, problem is that they both change the same file (as did the
product ID patch) and that changes the line numbers...
Against which sources should I take them again and should I start from the same clean sources for
each patch or can they be "stacked" ?
Greets.
Jan.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-02 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 9:44 [PATCH] hso: fix for the 'invalid frame length' messages Jan Dumon
2009-04-02 8:20 ` David Miller
[not found] ` <20090402.012032.67869929.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-04-02 8:34 ` Jan Dumon [this message]
[not found] ` <49D4787A.6060808-x9gZzRpC1QbQT0dZR+AlfA@public.gmane.org>
2009-04-02 8:36 ` David Miller
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=49D4787A.6060808@option.com \
--to=j.dumon-x9gzzrpc1qbqt0dzr+alfa@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).