From: Ben Greear <greearb@candelatech.com>
To: jeffrey.t.kirsher@intel.com
Cc: Jeff Kirsher <tarbal@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 1/5] send-crc: Add framework to allow sending packets with customized CRC.
Date: Wed, 08 Feb 2012 07:55:30 -0800 [thread overview]
Message-ID: <4F329AF2.3010202@candelatech.com> (raw)
In-Reply-To: <4F322C2C.1010708@gmail.com>
On 02/08/2012 12:02 AM, Jeff Kirsher wrote:
> On 02/07/2012 11:49 AM, greearb@candelatech.com wrote:
>> From: Ben Greear<greearb@candelatech.com>
>>
>> This is useful for testing RX handling of frames with bad
>> CRCs.
>>
>> Requires driver support to actually put the packet on the
>> wire properly.
>>
>> Signed-off-by: Ben Greear<greearb@candelatech.com>
> Ben-
>
> I tried to apply this series to Dave's net-next tree and I stopped after
> the first two patches did not apply cleanly.
>
> What tree did you use to generate this patch series?
I was using net-next from a few days ago...I'll rebase later today to
make sure everything is up to date and re-post.
Oh, that set is on top of the first two patches that enable rx-crc
infrastructure and e100 support..that might be the issue.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-02-08 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 19:49 [PATCH 1/5] send-crc: Add framework to allow sending packets with customized CRC greearb
2012-02-07 19:49 ` [PATCH 2/5] e100: Support sending custom Ethernet CRC greearb
2012-02-07 19:49 ` [PATCH 3/5] e1000e: " greearb
2012-02-07 20:33 ` [PATCH 1/5] send-crc: Add framework to allow sending packets with customized CRC Michał Mirosław
2012-02-07 20:43 ` Ben Greear
2012-02-07 23:59 ` Michał Mirosław
2012-02-08 0:06 ` Ben Greear
2012-02-08 8:02 ` Jeff Kirsher
2012-02-08 15:55 ` Ben Greear [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=4F329AF2.3010202@candelatech.com \
--to=greearb@candelatech.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tarbal@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.