From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: netdev@vger.kernel.org, wimax@linuxwimax.org
Subject: [net-2.6 2.6.33] WiMAX pull request
Date: Fri, 22 Jan 2010 15:14:40 -0800 [thread overview]
Message-ID: <cover.1264138318.git.inaky@linux.intel.com> (raw)
It might be quite late already for this (conceptually) one liner
patch, submitting just in case. This was a last minute issue we found,
were some i6050 parts have different USB IDs.
The following changes since commit b94b50289622e816adc9f94111cfc2679c80177c:
Jesse Brandeburg (1):
e1000e: enhance frame fragment detection
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/inaky/wimax.git linux-2.6.33.y
Patches follow for reviewing convenience.
Inaky Perez-Gonzalez (1):
wimax/i2400m: Add support for more i6x50 SKUs
drivers/net/wimax/i2400m/i2400m-usb.h | 2 ++
drivers/net/wimax/i2400m/usb.c | 12 +++++++++++-
2 files changed, 13 insertions(+), 1 deletions(-)
next reply other threads:[~2010-01-22 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 23:14 Inaky Perez-Gonzalez [this message]
2010-01-22 23:14 ` [net-2.6 2.6.33] wimax/i2400m: Add support for more i6x50 SKUs Inaky Perez-Gonzalez
2010-01-23 9:08 ` [net-2.6 2.6.33] WiMAX pull request 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=cover.1264138318.git.inaky@linux.intel.com \
--to=inaky@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=wimax@linuxwimax.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).