From: "Dmitry Kravkov" <dmitry@broadcom.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: eilong@broadcom.com
Subject: [PATCH net-next 0/7] bnx2x: move bnx2x to separate folder and divide to files
Date: Tue, 27 Jul 2010 22:01:38 +0300 [thread overview]
Message-ID: <1280257298.8566.8.camel@lb-tlvb-dmitry> (raw)
Hi,
Please consider applying following patch series to the net-next.
The series creates separate folder for bxn2x files and divides
bnx2x_main file into several logical parts:
bnx2x_cmn.[ch] - common functionality for PF and upcommimg
VF drivers
bnx2x_stat.[ch] - statistics handling
ethtool.c - ethtool related function and structs
After applying this series, integration of latest bnx2x patches
from net-2.6 which include fixes for statistics handling can't
be performed in a "automatic" way then i can suggest to re-submitting
these two patches.
Dmitry
---
next reply other threads:[~2010-07-27 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 19:01 Dmitry Kravkov [this message]
2010-07-27 20:09 ` [PATCH net-next 0/7] bnx2x: move bnx2x to separate folder and divide to files Dmitry Kravkov
2010-07-27 20:16 ` David Miller
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=1280257298.8566.8.camel@lb-tlvb-dmitry \
--to=dmitry@broadcom.com \
--cc=davem@davemloft.net \
--cc=eilong@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