All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
Cc: gregkh@linuxfoundation.org, joe@perches.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/11] staging: rtl8192e: Remove dead code: rtl_dm.[ch]
Date: Thu, 4 Jun 2015 16:52:08 +0300	[thread overview]
Message-ID: <20150604135208.GF28762@mwanda> (raw)
In-Reply-To: <1433278095-13988-7-git-send-email-mateusz.kulikowski@gmail.com>

On Tue, Jun 02, 2015 at 10:48:10PM +0200, Mateusz Kulikowski wrote:
> - Remove unused fields in dig_t structures. Some of them were only
>   initialized and never accessed.
> - Remove unused enums/macros/defines in rtl_dm.h
> - Remove duplicated function declarations
> - Remove unused dm_change_dynamic_initgain_thresh() function
> - Remove unused dm_shadow_init() function

Could you delete dm_shadow[] in a follow on patch.

How I review these sorts of patches is that:
1) Ignore deleted variables.  If those are used then it will cause a
   compile problem so I don't worry about it.

2) Verify that when we delete initialization, then we also delete the
   variable.  In this case we deleted the initialization of dm_shadow[]
   but not the variable itself, so I wondered if we were using
   unitialized data.  It turns out that it was just an oversight.

Reviewing these means a lot of searching, for each variable.  Next time
if the patch were split up more it would make it a bit easier.

regards,
dan carpenter


  reply	other threads:[~2015-06-04 13:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 20:48 [PATCH 00/11] staging: rtl8192e: Remove dead code Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 01/11] " Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 02/11] staging: rtl8192e: Remove dead code: cmpk_handle_query_config_rx() Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 03/11] staging: rtl8192e: Remove dead code: cmpk_message_handle_rx() Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 04/11] staging: rtl8192e: Remove dead code: read/write_cam Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 05/11] staging: rtl8192e: Remove unused macros/structures in rtl_core.h Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 06/11] staging: rtl8192e: Remove dead code: rtl_dm.[ch] Mateusz Kulikowski
2015-06-04 13:52   ` Dan Carpenter [this message]
2015-06-07 19:34     ` Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 07/11] staging: rtl8192e: Remove dead code: dig_t::dbg_mode Mateusz Kulikowski
2015-06-03  7:26   ` Sudip Mukherjee
2015-06-03 18:21     ` Mateusz Kulikowski
2015-06-04  5:18       ` Sudip Mukherjee
2015-06-04  5:50         ` Mateusz Kulikowski
2015-06-04  6:06           ` Sudip Mukherjee
2015-06-07 19:28             ` Mateusz Kulikowski
2015-06-04 13:53         ` Dan Carpenter
2015-06-02 20:48 ` [PATCH 08/11] staging: rtl8192e: Remove dead code: rt_stats Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 09/11] staging: rtl8192e: Remove dead code: undefined arrays Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 10/11] staging: rtl8192e: Remove dead code: r8192_priv members Mateusz Kulikowski
2015-06-02 20:48 ` [PATCH 11/11] staging: rtl8192e: Remove dead code: mp_adapter Mateusz Kulikowski

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=20150604135208.GF28762@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mateusz.kulikowski@gmail.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.