From: David Miller <davem@davemloft.net>
To: izumi.taku@jp.fujitsu.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] FUJITSU Extended Socket driver version 1.2
Date: Fri, 14 Oct 2016 12:05:14 -0400 (EDT) [thread overview]
Message-ID: <20161014.120514.100603981953874241.davem@davemloft.net> (raw)
In-Reply-To: <1476444345-28673-1-git-send-email-izumi.taku@jp.fujitsu.com>
From: Taku Izumi <izumi.taku@jp.fujitsu.com>
Date: Fri, 14 Oct 2016 20:25:44 +0900
> This patchset updates FUJITSU Extended Socket network driver into version 1.2.
> This includes the following enhancements:
> - ethtool -d support
> - ethtool -S enhancement
> - ethtool -w/-W support
> - Add some debugging feature (tracepoints etc)
>
> v1 -> v2:
> - Use u64 instead of phys_addr_t as TP_STRUCT__entry
> - Use ethtool facility to achieve debug mode instead of using debugfs
Series applied, thanks.
prev parent reply other threads:[~2016-10-14 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 11:25 [PATCH net-next v2 0/6] FUJITSU Extended Socket driver version 1.2 Taku Izumi
2016-10-14 11:27 ` [PATCH net-next v2 1/6] fjes: ethtool -d support for fjes driver Taku Izumi
2016-10-14 11:27 ` [PATCH net-next v2 2/6] fjes: Enhance ethtool -S " Taku Izumi
2016-10-14 11:27 ` [PATCH net-next v2 3/6] fjes: Add tracepoints in " Taku Izumi
2016-10-14 11:27 ` [PATCH net-next v2 4/6] fjes: ethtool -w and -W support for " Taku Izumi
2016-10-14 11:28 ` [PATCH net-next v2 5/6] fjes: Add debugfs entry for EP status information in " Taku Izumi
2016-10-14 11:28 ` [PATCH net-next v2 6/6] fjes: Update fjes driver version : 1.2 Taku Izumi
2016-10-14 16:05 ` David Miller [this message]
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=20161014.120514.100603981953874241.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=izumi.taku@jp.fujitsu.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).