netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: frank.blaschka@de.ibm.com
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [patch 0/3] s390: qeth patches for 2.6.35
Date: Wed, 12 May 2010 07:34:44 +0200	[thread overview]
Message-ID: <20100512053444.035939000@de.ibm.com> (raw)

Hi Dave,

here are some qeth patches for 2.6.35 (net-next).

shortlog:
Ursula Braun (1)
qeth: new message if OLM limit is reached

Frank Blaschka (2)
qeth: exploit HW TX checksumming
qeth: synchronize configuration interface

Thanks,
        Frank

             reply	other threads:[~2010-05-12  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12  5:34 frank.blaschka [this message]
2010-05-12  5:34 ` [patch 1/3] [PATCH] qeth: exploit HW TX checksumming frank.blaschka
2010-05-12  5:34 ` [patch 2/3] [PATCH] qeth: new message if OLM limit is reached frank.blaschka
2010-05-12  5:34 ` [patch 3/3] [PATCH] qeth: synchronize configuration interface frank.blaschka
2010-05-16  7:50 ` [patch 0/3] s390: qeth patches for 2.6.35 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=20100512053444.035939000@de.ibm.com \
    --to=frank.blaschka@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.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).