From: Dan Carpenter <dan.carpenter@oracle.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Himadri Pandya <himadri18.07@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Colin Ian King <colin.king@canonical.com>,
devel@driverdev.osuosl.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 -next] staging: rtl8192e: Remove set but not used variables 'broad_addr, stype'
Date: Mon, 18 Feb 2019 15:05:50 +0000 [thread overview]
Message-ID: <20190218150550.GG17104@kadam> (raw)
In-Reply-To: <20190218151543.145958-1-yuehaibing@huawei.com>
Fantastic! Thanks.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Himadri Pandya <himadri18.07@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Colin Ian King <colin.king@canonical.com>,
devel@driverdev.osuosl.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 -next] staging: rtl8192e: Remove set but not used variables 'broad_addr, stype'
Date: Mon, 18 Feb 2019 18:05:50 +0300 [thread overview]
Message-ID: <20190218150550.GG17104@kadam> (raw)
In-Reply-To: <20190218151543.145958-1-yuehaibing@huawei.com>
Fantastic! Thanks.
regards,
dan carpenter
next prev parent reply other threads:[~2019-02-18 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 12:33 [PATCH -next] staging: rtl8192e: Remove set but not used variables 'broad_addr, stype' YueHaibing
2019-02-18 12:33 ` YueHaibing
2019-02-18 14:31 ` Dan Carpenter
2019-02-18 14:31 ` Dan Carpenter
2019-02-18 14:48 ` YueHaibing
2019-02-18 14:48 ` YueHaibing
2019-02-18 15:15 ` [PATCH v2 " YueHaibing
2019-02-18 15:15 ` YueHaibing
2019-02-18 15:05 ` Dan Carpenter [this message]
2019-02-18 15:05 ` Dan Carpenter
2019-04-06 3:11 ` [PATCH -next] staging: rtl8192e: Remove set but not used variable 'VenderID' YueHaibing
2019-04-06 3:11 ` YueHaibing
2019-04-06 8:22 ` Mukesh Ojha
2019-04-06 8:34 ` Mukesh Ojha
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=20190218150550.GG17104@kadam \
--to=dan.carpenter@oracle.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=himadri18.07@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@huawei.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.