From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Frank Li <Frank.li@nxp.com>
Cc: vkoul@kernel.org, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom: gpi: remove unused struct 'gpi_desc'
Date: Thu, 16 May 2024 15:25:12 +0000 [thread overview]
Message-ID: <ZkYlWIg74EqHUFAp@gallifrey> (raw)
In-Reply-To: <ZkYdDtoPMnYlGT/6@lizhi-Precision-Tower-5810>
* Frank Li (Frank.li@nxp.com) wrote:
> On Thu, May 16, 2024 at 02:32:11PM +0100, linux@treblig.org wrote:
> > From: "Dr. David Alan Gilbert" <linux@treblig.org>
> >
> > 'gpi_desc' seems like it was never used.
> > Remove it.
>
> code change show 'reg_info', not 'gpi_desc'. You need make sure that it
> really is not used, not "seems like".
Oops that was a cut-and-paste when I did the commit on the name.
It was build tested.
V2 coming along now.
Dave
> 'struct reg_info' is never used, so remove it.
>
> >
> > Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> > ---
> > drivers/dma/qcom/gpi.c | 6 ------
> > 1 file changed, 6 deletions(-)
> >
> > diff --git a/drivers/dma/qcom/gpi.c b/drivers/dma/qcom/gpi.c
> > index 1c93864e0e4d..639ab304db9b 100644
> > --- a/drivers/dma/qcom/gpi.c
> > +++ b/drivers/dma/qcom/gpi.c
> > @@ -476,12 +476,6 @@ struct gpi_dev {
> > struct gpii *gpiis;
> > };
> >
> > -struct reg_info {
> > - char *name;
> > - u32 offset;
> > - u32 val;
> > -};
> > -
> > struct gchan {
> > struct virt_dma_chan vc;
> > u32 chid;
> > --
> > 2.45.0
> >
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
prev parent reply other threads:[~2024-05-16 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 13:32 [PATCH] dmaengine: qcom: gpi: remove unused struct 'gpi_desc' linux
2024-05-16 14:49 ` Frank Li
2024-05-16 15:25 ` Dr. David Alan Gilbert [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=ZkYlWIg74EqHUFAp@gallifrey \
--to=linux@treblig.org \
--cc=Frank.li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
/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