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, alan@linux.intel.com,
Mark Einon <mark.einon@gmail.com>
Subject: [PATCH 5/6] staging: et131x: Remove header declaration of et131x_check_mii()
Date: Sun, 25 Sep 2011 19:17:56 +0100 [thread overview]
Message-ID: <1316974677-17108-5-git-send-email-mark.einon@gmail.com> (raw)
In-Reply-To: <1316974677-17108-1-git-send-email-mark.einon@gmail.com>
et131x_check_mii no longer exists, remove its declaration from the header file
Signed-off-by: Mark Einon <mark.einon@gmail.com>
---
drivers/staging/et131x/et131x.h | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/et131x/et131x.h b/drivers/staging/et131x/et131x.h
index 6f8fef6..c047e6e 100644
--- a/drivers/staging/et131x/et131x.h
+++ b/drivers/staging/et131x/et131x.h
@@ -107,8 +107,6 @@ int32_t et131x_mii_read(struct et131x_adapter *adapter,
u8 reg, u16 *value);
int32_t et131x_mii_write(struct et131x_adapter *adapter,
u8 reg, u16 value);
-void et131x_mii_check(struct et131x_adapter *adapter,
- u16 bmsr, u16 bmsr_ints);
int et131x_mdio_read(struct mii_bus *bus, int phy_addr, int reg);
int et131x_mdio_write(struct mii_bus *bus, int phy_addr, int reg, u16 value);
--
1.7.6
next prev parent reply other threads:[~2011-09-25 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 18:17 [PATCH 1/6] staging: et131x: support register dump in ethtool ops Mark Einon
2011-09-25 18:17 ` [PATCH 2/6] staging: et131x: Add link status to adapter struct Mark Einon
2011-09-25 18:17 ` [PATCH 3/6] staging: et131x: Remove et131x_check_mii() and move functionality into et131x_adjust_link() Mark Einon
2011-09-25 18:17 ` [PATCH 4/6] staging: et131x: Create et131x_[dis|en]able_txrx() calls Mark Einon
2011-09-25 18:17 ` Mark Einon [this message]
2011-09-25 18:17 ` [PATCH 6/6] staging: et131x: Bugfix - driver doesn't autoreneg after cable unplug/plug events 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=1316974677-17108-5-git-send-email-mark.einon@gmail.com \
--to=mark.einon@gmail.com \
--cc=alan@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®