The patch titled
drivers/net/cxgb3: remove several unneeded zero initialization
has been removed from the -mm tree. Its filename was
drivers-net-cxgb3-remove-several-unneeded-zero-initialization.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: drivers/net/cxgb3: remove several unneeded zero initialization
From: Denis Cheng <crquan@xxxxxxxxx>
Signed-off-by: Denis Cheng <crquan@xxxxxxxxx>
Cc: <linux-bugs@xxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/net/cxgb3/cxgb3_main.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff -puN drivers/net/cxgb3/cxgb3_main.c~drivers-net-cxgb3-remove-several-unneeded-zero-initialization drivers/net/cxgb3/cxgb3_main.c
--- a/drivers/net/cxgb3/cxgb3_main.c~drivers-net-cxgb3-remove-several-unneeded-zero-initialization
+++ a/drivers/net/cxgb3/cxgb3_main.c
@@ -754,7 +754,7 @@ static int upgrade_fw(struct adapter *ad
*/
static int cxgb_up(struct adapter *adap)
{
- int err = 0;
+ int err;
if (!(adap->flags & FULL_INIT_DONE)) {
err = t3_check_fw_version(adap);
@@ -861,7 +861,7 @@ static int offload_open(struct net_devic
struct adapter *adapter = dev->priv;
struct t3cdev *tdev = T3CDEV(dev);
int adap_up = adapter->open_device_map & PORT_MASK;
- int err = 0;
+ int err;
if (test_and_set_bit(OFFLOAD_DEVMAP_BIT, &adapter->open_device_map))
return 0;
@@ -1502,7 +1502,7 @@ static int set_eeprom(struct net_device
u8 * data)
{
u8 *buf;
- int err = 0;
+ int err;
u32 aligned_offset, aligned_len, *p;
struct adapter *adapter = dev->priv;
_
Patches currently in -mm which might be from crquan@xxxxxxxxx are
git-gfs2-nmw.patch
git-netdev-all.patch
nbd-use-list_for_each_entry_safe-to-make-it-more-consolidated-and-readable.patch
nbd-change-a-parameters-type-to-remove-a-memcpy-call.patch
fs-use-kmem_cache_zalloc-instead.patch
fs-remove-the-unused-mempages-parameter.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
