From: Takashi Iwai <tiwai@suse.de>
To: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound: drivers: portman2x4.c: Remove some unused functions
Date: Fri, 02 Jan 2015 09:17:12 +0100 [thread overview]
Message-ID: <s5hfvbtfvg7.wl-tiwai@suse.de> (raw)
In-Reply-To: <1420125165-26527-1-git-send-email-rickard_strandqvist@spectrumdigital.se>
At Thu, 1 Jan 2015 16:12:45 +0100,
Rickard Strandqvist wrote:
>
> Removes some functions that are not used anywhere:
> portman_read_data() portman_read_command()
>
> This was partially found by using a static code analysis program called cppcheck.
>
> Signed-off-by: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
> ---
> sound/drivers/portman2x4.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/sound/drivers/portman2x4.c b/sound/drivers/portman2x4.c
> index 78ccfa4..b5b6b4e 100644
> --- a/sound/drivers/portman2x4.c
> +++ b/sound/drivers/portman2x4.c
> @@ -198,21 +198,11 @@ static inline void portman_write_command(struct portman *pm, u8 value)
> parport_write_control(pm->pardev->port, value);
> }
>
> -static inline u8 portman_read_command(struct portman *pm)
> -{
> - return parport_read_control(pm->pardev->port);
> -}
> -
> static inline u8 portman_read_status(struct portman *pm)
> {
> return parport_read_status(pm->pardev->port);
> }
>
> -static inline u8 portman_read_data(struct portman *pm)
> -{
> - return parport_read_data(pm->pardev->port);
> -}
> -
> static inline void portman_write_data(struct portman *pm, u8 value)
> {
> parport_write_data(pm->pardev->port, value);
Rickard, your works are highly appreciated, but please think twice
before submitting patches: is it worth for the whole?
For example, in this case: the removals are static inline functions.
So there is no gain by removing this regarding the object size. OTOH,
they are obviously wrapper accessors, thus dropping blindly would
result in inconsistency. That is, a reader may wonder later why some
are write only and some not.
thanks,
Takashi
prev parent reply other threads:[~2015-01-02 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 15:12 Rickard Strandqvist
2015-01-02 8:17 ` Takashi Iwai [this message]
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=s5hfvbtfvg7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rickard_strandqvist@spectrumdigital.se \
/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
all inboxes | Powered by JetHome®