From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] cnic: Remove duplicate bnx2x definitions
Date: Wed, 04 Sep 2013 00:53:24 -0400 (EDT) [thread overview]
Message-ID: <20130904.005324.1832650483000329165.davem@davemloft.net> (raw)
In-Reply-To: <1378147352-9076-1-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Mon, 2 Sep 2013 11:42:27 -0700
> Adapt the code to use existing macros and struct fields in bnx2x.h to
> avoid duplication.
Series applied, thanks.
prev parent reply other threads:[~2013-09-04 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 18:42 [PATCH net-next 0/5] cnic: Remove duplicate bnx2x definitions Michael Chan
2013-09-02 18:42 ` [PATCH net-next 1/5] cnic: Use CHIP_NUM macros from bnx2x.h Michael Chan
2013-09-02 18:42 ` [PATCH net-next 2/5] cnic: Redefine BNX2X_HW_CID using existing bnx2x macros Michael Chan
2013-09-02 18:42 ` [PATCH net-next 3/5] cnic: Eliminate CNIC_PORT macro and port_mode in local struct Michael Chan
2013-09-02 18:42 ` [PATCH net-next 4/5] cnic: Eliminate local copy of pfid Michael Chan
2013-09-02 18:42 ` [PATCH net-next 5/5] cnic: Update version to 2.5.18 Michael Chan
2013-09-04 4:53 ` 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=20130904.005324.1832650483000329165.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.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).