netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Blaschka <blaschka@linux.vnet.ibm.com>
To: "Michał Mirosław" <mirq@rere.qmqm.pl>
Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [patch 1/9] [PATCH] qeth: convert to hw_features part 2
Date: Fri, 13 May 2011 09:57:10 +0200	[thread overview]
Message-ID: <20110513075710.GA41213@tuxmaker.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20110513073807.GA18312@rere.qmqm.pl>

On Fri, May 13, 2011 at 09:38:07AM +0200, Michał Mirosław wrote:
> On Fri, May 13, 2011 at 06:45:01AM +0200, frank.blaschka@de.ibm.com wrote:
> > From: Frank Blaschka <frank.blaschka@de.ibm.com>
> > Set rx csum default to hw checksumming again.
> > Remove sysfs interface for rx csum (checksumming) and TSO (large_send).
> > With the new hw_features it does not work to keep the old sysfs
> > interface in parallel. Convert options.checksum_type to new hw_features.
> 
> Please see following patch (replacing qeth_l3_main.c part of your patch) for
> an illustration of my earlier comments.
>

Thx for the illustration. I will review and do some more testing. For now
Dave should apply my latest patch set so we get this stuff into next merge
window. 

  reply	other threads:[~2011-05-13  7:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13  4:45 [patch 0/9] [resend v2] s390: network feature patches for net-next frank.blaschka
2011-05-13  4:45 ` [patch 1/9] [PATCH] qeth: convert to hw_features part 2 frank.blaschka
2011-05-13  7:38   ` Michał Mirosław
2011-05-13  7:57     ` Frank Blaschka [this message]
2011-05-13  8:07   ` Michał Mirosław
2011-05-13  4:45 ` [patch 2/9] [PATCH] qeth: add OSA concurrent hardware trap frank.blaschka
2011-05-13  4:45 ` [patch 3/9] [PATCH] qeth: add owner to ccw driver frank.blaschka
2011-05-13  4:45 ` [patch 4/9] [PATCH] claw: remove unused return code handling frank.blaschka
2011-05-13  4:45 ` [patch 5/9] [PATCH] lcs: get rid of compile warning frank.blaschka
2011-05-13  4:45 ` [patch 6/9] [PATCH] ctcm: " frank.blaschka
2011-05-13  4:45 ` [patch 7/9] [PATCH] iucv: " frank.blaschka
2011-05-13  4:45 ` [patch 8/9] [PATCH] af_iucv: " frank.blaschka
2011-05-13  4:45 ` [patch 9/9] [PATCH] convert old cpumask API into new one frank.blaschka
2011-05-13 18:55 ` [patch 0/9] [resend v2] s390: network feature patches for net-next David Miller
  -- strict thread matches above, loose matches on Subject: below --
2011-05-12  5:43 [patch 0/9] [resend] " frank.blaschka
2011-05-12  5:43 ` [patch 1/9] [PATCH] qeth: convert to hw_features part 2 frank.blaschka
2011-05-12  5:59   ` Michał Mirosław
2011-05-12  7:21     ` Frank Blaschka
2011-05-12  8:12       ` Michał Mirosław
2011-05-12 11:10         ` Frank Blaschka
2011-05-12 11:25           ` Michał Mirosław
2011-05-12 11:59             ` Frank Blaschka
2011-05-12 22:02               ` David Miller
2011-05-10 11:50 [patch 0/9] s390: network feature patches for net-next frank.blaschka
2011-05-10 11:50 ` [patch 1/9] [PATCH] qeth: convert to hw_features part 2 frank.blaschka
2011-05-10 13:19   ` Michał Mirosław
2011-05-10 14:09     ` Frank Blaschka
2011-05-10 14:33       ` Michał Mirosław

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=20110513075710.GA41213@tuxmaker.boeblingen.de.ibm.com \
    --to=blaschka@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-s390@vger.kernel.org \
    --cc=mirq@rere.qmqm.pl \
    --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).