From: Joe Perches <joe@perches.com>
To: Aliya Rahmani <aliyarahmani786@gmail.com>, mchehab@kernel.org
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
outreachy@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: media: av7110: remove redundant space after cast
Date: Mon, 18 Apr 2022 12:22:36 -0700 [thread overview]
Message-ID: <24b3a1f5c1fa416ac5aed375afaa03c0c3ce2be1.camel@perches.com> (raw)
In-Reply-To: <20220418170900.16725-1-aliyarahmani786@gmail.com>
On Mon, 2022-04-18 at 22:39 +0530, Aliya Rahmani wrote:
> Remove the unnecessary space immediately after a cast. Identified by
> checkpatch: CHECK: No space is necessary after a cast.
[]
> diff --git a/drivers/staging/media/av7110/av7110_av.c b/drivers/staging/media/av7110/av7110_av.c
[]
> @@ -93,7 +93,7 @@ int av7110_record_cb(struct dvb_filter_pes2ts *p2t, u8 *buf, size_t len)
>
> static int dvb_filter_pes2ts_cb(void *priv, unsigned char *data)
> {
> - struct dvb_demux_feed *dvbdmxfeed = (struct dvb_demux_feed *) priv;
> + struct dvb_demux_feed *dvbdmxfeed = (struct dvb_demux_feed *)priv;
It's also unnecessary to cast void pointers so the cast could be removed.
struct dvb_demux_feed *dvbdmxfeed = priv;
And the code here uses dvbdmxfeed and feed rather interchangeably for
uses of a struct dvb_demux_feed *.
It might be better just to use feed and change the other uses too.
Do consider this just a coding exercise as the driver is for some
hardware that is effectively dead/unavailable/non-functional.
Look at:
commit 989cf18ed08f8b6efd1d1592d1d0108fa09b98f5
Author: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Date: Mon May 31 17:27:09 2021 +0200
media: av7110: move driver to staging
This driver is really old, from devices that aren't
manufactured anymore for more than a decade.
Maybe instead consider adding a MAINTAINERS section
suggesting this is obsolete and/or a TODO entry in this
directory saying "Delete this" after some time.
prev parent reply other threads:[~2022-04-18 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 17:09 Aliya Rahmani
2022-04-18 19:22 ` Joe Perches [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=24b3a1f5c1fa416ac5aed375afaa03c0c3ce2be1.camel@perches.com \
--to=joe@perches.com \
--cc=aliyarahmani786@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=outreachy@lists.linux.dev \
/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®