From: Richard Cochran <richardcochran@gmail.com>
To: netdev@vger.kernel.org
Cc: Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com>,
David Miller <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
Michal Simek <michal.simek@xilinx.com>
Subject: [PATCH net-next 0/3] net: axienet: Fix random driver issues.
Date: Mon, 16 Dec 2019 10:32:53 -0800 [thread overview]
Message-ID: <cover.1576520432.git.richardcochran@gmail.com> (raw)
While working on the PTP P2P 1-step series, my hardware under test
just happened to be connected with an axienet MAC. This series
address three unrelated issues in the driver.
Thanks,
Richard
Richard Cochran (3):
net: axienet: Propagate registration errors during probe.
net: axienet: Support software transmit time stamping.
net: axienet: Pass ioctls to the phy.
.../net/ethernet/xilinx/xilinx_axienet_main.c | 32 ++++++++++++++++---
1 file changed, 28 insertions(+), 4 deletions(-)
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Richard Cochran <richardcochran@gmail.com>
To: netdev@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
David Miller <davem@davemloft.net>,
Michal Simek <michal.simek@xilinx.com>,
Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com>
Subject: [PATCH net-next 0/3] net: axienet: Fix random driver issues.
Date: Mon, 16 Dec 2019 10:32:53 -0800 [thread overview]
Message-ID: <cover.1576520432.git.richardcochran@gmail.com> (raw)
While working on the PTP P2P 1-step series, my hardware under test
just happened to be connected with an axienet MAC. This series
address three unrelated issues in the driver.
Thanks,
Richard
Richard Cochran (3):
net: axienet: Propagate registration errors during probe.
net: axienet: Support software transmit time stamping.
net: axienet: Pass ioctls to the phy.
.../net/ethernet/xilinx/xilinx_axienet_main.c | 32 ++++++++++++++++---
1 file changed, 28 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2019-12-16 18:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 18:32 Richard Cochran [this message]
2019-12-16 18:32 ` [PATCH net-next 0/3] net: axienet: Fix random driver issues Richard Cochran
2019-12-16 18:32 ` [PATCH net-next 1/3] net: axienet: Propagate registration errors during probe Richard Cochran
2019-12-16 18:32 ` Richard Cochran
2019-12-17 6:19 ` Radhey Shyam Pandey
2019-12-17 6:19 ` Radhey Shyam Pandey
2019-12-17 15:49 ` Richard Cochran
2019-12-17 15:49 ` Richard Cochran
2019-12-19 18:13 ` Radhey Shyam Pandey
2019-12-19 18:13 ` Radhey Shyam Pandey
2019-12-20 5:19 ` Richard Cochran
2019-12-20 5:19 ` Richard Cochran
2019-12-20 5:51 ` Radhey Shyam Pandey
2019-12-20 5:51 ` Radhey Shyam Pandey
2019-12-16 18:32 ` [PATCH net-next 2/3] net: axienet: Support software transmit time stamping Richard Cochran
2019-12-16 18:32 ` Richard Cochran
2019-12-16 18:32 ` [PATCH net-next 3/3] net: axienet: Pass ioctls to the phy Richard Cochran
2019-12-16 18:32 ` Richard Cochran
2019-12-17 6:43 ` Radhey Shyam Pandey
2019-12-17 6:43 ` Radhey Shyam Pandey
2019-12-17 10:59 ` Andrew Lunn
2019-12-17 10:59 ` Andrew Lunn
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.1576520432.git.richardcochran@gmail.com \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=radhey.shyam.pandey@xilinx.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.