From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org, peppe.cavallaro@st.com,
netdev@vger.kernel.org
Cc: giancarlo.asnaghi@st.com
Subject: [PATCH 0/3] stmmac patches
Date: Tue, 24 Jan 2012 10:08:45 +0100 [thread overview]
Message-ID: <cover.1327394750.git.rubini@gnudd.com> (raw)
The following three patches add support for the STA2X11 device in the
stmmac driver. The device is a PCI-e bridge, so I need just to
add my identifiers. The identifiers being added are already in pci_ids
of linux-next.
The second patch is a cleanup, already acked by both authors.
As for the third, I noted that there is "#ifndef MODULE" adding
__setup directives, but the module parameters already work, and I
successfully use stmmac.phy_id=1 to boot my system, so the __setup
adre just duplicates. This has not been acked by Giuseppe Cavallaro
but I offer it here nonetheless.
Alessandro Rubini (3):
stmmac: added PCI identifiers
stmmac: err out on second probe; use precompiled static structures
stmmac: remove kernel cmdline parsing
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 59 ---------------------
drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c | 53 ++++++++++--------
2 files changed, 29 insertions(+), 83 deletions(-)
--
1.7.7.2
next reply other threads:[~2012-01-24 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 9:08 Alessandro Rubini [this message]
2012-01-24 9:08 ` [PATCH 1/3] stmmac: added PCI identifiers Alessandro Rubini
2012-01-24 9:09 ` [PATCH 2/3] stmmac: err out on second probe; use precompiled static structures Alessandro Rubini
2012-01-24 9:09 ` [PATCH 3/3] stmmac: remove kernel cmdline parsing Alessandro Rubini
2012-01-24 20:43 ` [PATCH 0/3] stmmac patches David Miller
2012-01-24 20:47 ` Alessandro Rubini
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=cover.1327394750.git.rubini@gnudd.com \
--to=rubini@gnudd.com \
--cc=giancarlo.asnaghi@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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;
as well as URLs for NNTP newsgroup(s).