From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, gospo@redhat.com,
Tom Herbert <therbert@google.com>,
Bruce Allan <bruce.w.allan@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-next-2.6 PATCH 3/4] e1000e: Remove unnessary log message
Date: Wed, 05 May 2010 17:03:11 -0700 [thread overview]
Message-ID: <20100506000309.8042.9387.stgit@localhost.localdomain> (raw)
In-Reply-To: <20100506000221.8042.64794.stgit@localhost.localdomain>
From: Tom Herbert <therbert@google.com>
Remove e_info message printed whenever TSO is enabled or disabled.
This is not very useful and just clutters dmesg.
Signed-off-by: Tom Herbert <therbert@google.com>
Acked-by: Bruce Allan <bruce.w.allan@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
drivers/net/e1000e/ethtool.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/net/e1000e/ethtool.c b/drivers/net/e1000e/ethtool.c
index c81118a..6ff376c 100644
--- a/drivers/net/e1000e/ethtool.c
+++ b/drivers/net/e1000e/ethtool.c
@@ -412,7 +412,6 @@ static int e1000_set_tso(struct net_device *netdev, u32 data)
netdev->features &= ~NETIF_F_TSO6;
}
- e_info("TSO is %s\n", data ? "Enabled" : "Disabled");
adapter->flags |= FLAG_TSO_FORCE;
return 0;
}
next prev parent reply other threads:[~2010-05-06 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 0:02 [net-next-2.6 PATCH 1/4] e1000e: save skb counts in TX to avoid cache misses Jeff Kirsher
2010-05-06 0:02 ` [net-next-2.6 PATCH 2/4] e1000e: reduce writes of RX producer ptr Jeff Kirsher
2010-05-06 7:19 ` David Miller
2010-05-06 0:03 ` Jeff Kirsher [this message]
2010-05-06 7:19 ` [net-next-2.6 PATCH 3/4] e1000e: Remove unnessary log message David Miller
2010-05-06 0:03 ` [net-next-2.6 PATCH 4/4] e1000e: Save irq into netdev structure Jeff Kirsher
2010-05-06 7:19 ` David Miller
2010-05-06 7:19 ` [net-next-2.6 PATCH 1/4] e1000e: save skb counts in TX to avoid cache misses David Miller
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=20100506000309.8042.9387.stgit@localhost.localdomain \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).