All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Einon <mark.einon@gmail.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	o.hartmann@telovital.com
Subject: [PATCH 00/12] staging: et131x: Following mvoe to use phydev, remove detritus
Date: Sun,  4 Sep 2011 11:24:31 +0100	[thread overview]
Message-ID: <1315131883-11068-1-git-send-email-mark.einon@gmail.com> (raw)

These changes make a big cleanup of the PHY driver code, and removing stuff that isn't (hopefully) relevant anymore.  

Mark Einon (12):
staging: et131x: Remove private adapter->linkspeed and
staging: et131x: Remove private adapter->duplex_mode
staging: et131x: Remove redundant struct adapter
staging: et131x: Remove PHY interrupt handling code
staging: et131x: remove calls to
staging: et131x: Remove registry_rx_mem_end from
staging: et131x: Remove cached_mask_value from
staging: et131x: Remove duplicated register defines
staging: et131x: Replace magic numbers in et1310_phy.c
staging: et131x: Remove struct mi_regs from
staging: et131x: Remove ai_force_[duplex|speed] from
staging: et131x: Update README file

 drivers/staging/et131x/README           |    2 -
 drivers/staging/et131x/et1310_mac.c     |   15 ++-
 drivers/staging/et131x/et1310_phy.c     |  105 ++++++++++-------------
 drivers/staging/et131x/et1310_phy.h     |  143 +++++++++++++++----------------
 drivers/staging/et131x/et1310_rx.c      |    9 ++-
 drivers/staging/et131x/et1310_tx.c      |    6 +-
 drivers/staging/et131x/et131x_adapter.h |   13 ---
 drivers/staging/et131x/et131x_initpci.c |   16 ++--
 drivers/staging/et131x/et131x_isr.c     |   40 ---------
 9 files changed, 143 insertions(+), 206 deletions(-)


             reply	other threads:[~2011-09-04 10:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04 10:24 Mark Einon [this message]
2011-09-04 10:24 ` [PATCH 01/12] staging: et131x: Remove private adapter->linkspeed and use phydev->speed instead Mark Einon
2011-09-04 10:24 ` [PATCH 02/12] staging: et131x: Remove private adapter->duplex_mode and use phydev->duplex instead Mark Einon
2011-09-04 10:24 ` [PATCH 03/12] staging: et131x: Remove redundant struct adapter members Mark Einon
2011-09-04 10:24 ` [PATCH 04/12] staging: et131x: Remove PHY interrupt handling code from driver isr handler Mark Einon
2011-09-04 10:24 ` [PATCH 05/12] staging: et131x: remove calls to netif_carrier_[on|off] from et131x_mii_check Mark Einon
2011-09-04 10:24 ` [PATCH 06/12] staging: et131x: Remove registry_rx_mem_end from struct et131x_adapter Mark Einon
2011-09-04 10:24 ` [PATCH 07/12] staging: et131x: Remove cached_mask_value from et131x_adapter Mark Einon
2011-09-04 10:24 ` [PATCH 08/12] staging: et131x: Remove duplicated register defines from et1310_phy.h Mark Einon
2011-09-04 10:24 ` [PATCH 09/12] staging: et131x: Replace magic numbers in et1310_phy.c with defines Mark Einon
2011-09-04 10:24 ` [PATCH 10/12] staging: et131x: Remove struct mi_regs from et1310_phy.h Mark Einon
2011-09-04 10:24 ` [PATCH 11/12] staging: et131x: Remove ai_force_[duplex|speed] from et131x_adapter Mark Einon
2011-09-04 10:24 ` [PATCH 12/12] staging: et131x: Update README 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=1315131883-11068-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 \
    --cc=o.hartmann@telovital.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.