From: Mark Einon <mark.einon@gmail.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 00/10] staging: et131x: Move driver into one file
Date: Wed, 12 Oct 2011 22:36:32 +0100 [thread overview]
Message-ID: <1318455402-10596-1-git-send-email-mark.einon@gmail.com> (raw)
This patch set moves all driver code into one file, and all register defines
into one header file.
Mark Einon (10):
staging: et131x: Put all .c files into one big file
staging: et131x: Move function declarations from et131x.h to et131x.c
staging: et131x: Move non-register defines from et131x.h to et131x.c
staging: et131x: move et1310_address_map.h contents into et131x.h
staging: et131x: move et1310_phy.h contents into et131x.h
staging: et131x: move et131x_adapter.h contents into et131x.c
staging: et131x: move et131x_defs.h contents into et131x.c
staging: et131x: move et1310_rx.h contents into et131x.c
staging: et131x: move et1310_tx.h contents into et131x.c
staging: et131x: Update TODO list - remove 'put driver into single file'
drivers/staging/et131x/Makefile | 11 -
drivers/staging/et131x/README | 1 -
drivers/staging/et131x/et1310_address_map.h | 1436 -------
drivers/staging/et131x/et1310_eeprom.c | 408 --
drivers/staging/et131x/et1310_mac.c | 654 ----
drivers/staging/et131x/et1310_phy.c | 375 --
drivers/staging/et131x/et1310_phy.h | 292 --
drivers/staging/et131x/et1310_pm.c | 204 -
drivers/staging/et131x/et1310_rx.c | 1160 ------
drivers/staging/et131x/et1310_rx.h | 245 --
drivers/staging/et131x/et1310_tx.c | 793 ----
drivers/staging/et131x/et1310_tx.h | 150 -
drivers/staging/et131x/et131x.c | 5578 +++++++++++++++++++++++++++
drivers/staging/et131x/et131x.h | 1728 ++++++++-
drivers/staging/et131x/et131x_adapter.h | 218 --
drivers/staging/et131x/et131x_defs.h | 128 -
drivers/staging/et131x/et131x_ethtool.c | 201 -
drivers/staging/et131x/et131x_initpci.c | 950 -----
drivers/staging/et131x/et131x_isr.c | 442 ---
drivers/staging/et131x/et131x_netdev.c | 662 ----
20 files changed, 7203 insertions(+), 8433 deletions(-)
next reply other threads:[~2011-10-12 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 21:36 Mark Einon [this message]
2011-10-12 21:36 ` [PATCH 01/10] staging: et131x: Put all .c files into one big file Mark Einon
2011-10-17 22:29 ` Greg KH
2011-10-12 21:36 ` [PATCH 02/10] staging: et131x: Move function declarations from et131x.h to et131x.c Mark Einon
2011-10-12 21:36 ` [PATCH 03/10] staging: et131x: Move non-register defines " Mark Einon
2011-10-12 21:36 ` [PATCH 04/10] staging: et131x: move et1310_address_map.h contents into et131x.h Mark Einon
2011-10-12 21:36 ` [PATCH 05/10] staging: et131x: move et1310_phy.h " Mark Einon
2011-10-12 21:36 ` [PATCH 06/10] staging: et131x: move et131x_adapter.h contents into et131x.c Mark Einon
2011-10-12 21:36 ` [PATCH 07/10] staging: et131x: move et131x_defs.h " Mark Einon
2011-10-12 21:36 ` [PATCH 08/10] staging: et131x: move et1310_rx.h " Mark Einon
2011-10-12 21:36 ` [PATCH 09/10] staging: et131x: move et1310_tx.h " Mark Einon
2011-10-12 21:36 ` [PATCH 10/10] staging: et131x: Update TODO list - remove 'put driver into single file' Mark Einon
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=1318455402-10596-1-git-send-email-mark.einon@gmail.com \
--to=mark.einon@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@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