From: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
To: David Miller <davem@davemloft.net>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
netdev <netdev@vger.kernel.org>,
Dept_NX_Linux_NIC_Driver <Dept_NX_Linux_NIC_Driver@qlogic.com>,
Manish chopra <manish.chopra@qlogic.com>
Subject: [PATCH net-next] ethtool: Added a field fw dump_state
Date: Fri, 16 Mar 2012 10:58:30 -0700 [thread overview]
Message-ID: <1331920711-16049-1-git-send-email-anirban.chakraborty@qlogic.com> (raw)
From: Manish chopra <manish.chopra@qlogic.com>
This field is added to enable/disable firmware dump.
Signed-off-by: Manish chopra <manish.chopra@qlogic.com>
Signed-off-by: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
---
include/linux/ethtool.h | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/include/linux/ethtool.h b/include/linux/ethtool.h
index e1d9e0e..6ebc7de 100644
--- a/include/linux/ethtool.h
+++ b/include/linux/ethtool.h
@@ -666,15 +666,22 @@ struct ethtool_flash {
* %ETHTOOL_GET_DUMP_DATA and this is returned as dump length by driver
* for %ETHTOOL_GET_DUMP_FLAG command
* @data: data collected for get dump data operation
+ * @dump_state: state of the firmware dump. which can be enable/disable.
*/
+
+#define ETH_FW_DUMP_ENABLE 1
+#define ETH_FW_DUMP_DISABLE 0
+
struct ethtool_dump {
__u32 cmd;
__u32 version;
__u32 flag;
__u32 len;
__u8 data[0];
+ __u8 dump_state;
};
+
/* for returning and changing feature sets */
/**
--
1.7.1
next reply other threads:[~2012-03-16 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 17:58 Anirban Chakraborty [this message]
2012-03-16 17:58 ` [PATCH net-next] qlcnic: ethtool change to provide the dump_state information Anirban Chakraborty
2012-03-16 18:27 ` [PATCH net-next] ethtool: Added a field fw dump_state Ben Hutchings
2012-03-16 21:10 ` Anirban Chakraborty
2012-03-16 21:22 ` Eric Dumazet
2012-03-16 21:28 ` Anirban Chakraborty
2012-03-16 21:37 ` Ben Hutchings
2012-03-16 22:37 ` Anirban Chakraborty
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=1331920711-16049-1-git-send-email-anirban.chakraborty@qlogic.com \
--to=anirban.chakraborty@qlogic.com \
--cc=Dept_NX_Linux_NIC_Driver@qlogic.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=manish.chopra@qlogic.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).