netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH 11/12] sfc: Allow for additional checksum offload features
Date: Sun, 29 Nov 2009 00:01:04 -0800 (PST)	[thread overview]
Message-ID: <20091129.000104.109985484.davem@davemloft.net> (raw)
In-Reply-To: <1259422579.3709.12.camel@localhost>

From: Ben Hutchings <bhutchings@solarflare.com>
Date: Sat, 28 Nov 2009 15:36:19 +0000

> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>

You can add this patch when you actually have a chance in your
set that adds a value of ->offload_features other than NETIF_IP_CSUM.

So I'm setting aside this change for now, resubmit it along with
the change that actually needs to use different values.

Thanks.

      reply	other threads:[~2009-11-29  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28 15:36 [PATCH 11/12] sfc: Allow for additional checksum offload features Ben Hutchings
2009-11-29  8:01 ` David Miller [this message]

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=20091129.000104.109985484.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhutchings@solarflare.com \
    --cc=linux-net-drivers@solarflare.com \
    --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).