From: David Miller <davem@davemloft.net>
To: harvey.harrison@gmail.com
Cc: sbhatewara@vmware.com, netdev@vger.kernel.org, shemminger@vyatta.com
Subject: Re: [PATCHv2] vmxnet3: remove set_flag_le{16,64} helpers
Date: Thu, 21 Oct 2010 03:57:41 -0700 (PDT) [thread overview]
Message-ID: <20101021.035741.68130271.davem@davemloft.net> (raw)
In-Reply-To: <1287642721-5997-1-git-send-email-harvey.harrison@gmail.com>
From: Harvey Harrison <harvey.harrison@gmail.com>
Date: Wed, 20 Oct 2010 23:32:01 -0700
> It's easier to just annotate the constants as little endian types and set/clear
> the flags directly.
>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---i
> Sorry, missed a git add and left a line out of the previous patch.
Could you please rebase this against net-next-2.6 since I've
applied Stephen Hemminger's patch.
Thanks!
next prev parent reply other threads:[~2010-10-21 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 6:32 [PATCHv2] vmxnet3: remove set_flag_le{16,64} helpers Harvey Harrison
2010-10-21 10:57 ` David Miller [this message]
2010-10-21 15:24 ` Harvey Harrison
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=20101021.035741.68130271.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sbhatewara@vmware.com \
--cc=shemminger@vyatta.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 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).