All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Frank.li@nxp.com, vkoul@kernel.org,
	linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: qcom: gpi: remove unused struct 'reg_info'
Date: Fri, 17 May 2024 23:04:21 +0000	[thread overview]
Message-ID: <Zkfidbh3Sqy6BEDh@gallifrey> (raw)
In-Reply-To: <3fe6e86d-5b4d-4b3c-a5d7-59f01dc6b0bc@linaro.org>

* Bryan O'Donoghue (bryan.odonoghue@linaro.org) wrote:
> On 17/05/2024 12:19, Dr. David Alan Gilbert wrote:
> > > If you look at the V1 I had
> > > ''gpi_desc' seems like it was never used.
> > > Remove it.'
> > > 
> > > but Frank suggested copying the subject line; so I'm not sure
> > > whether you want more or less!
> > > 
> > > I could change this to:
> > > 
> > > 'gpi_desc' was never used since it's initial
> > > commit 5d0c3533a19f ("dmaengine: qcom: Add GPI dma driver")
> > Oops, of course I mean 'reg_info' which is what I fixed in v2.
> > 
> > > Would you be OK with that?
> > Dave
> > 
> > > Dave
> 
> Hi Dave,
> 
> I saw your v1 interaction after commenting but, I still think commits that
> say "this removes a data structure" should elaborate more.
> 
> "This structure is no longer used since commit: 12charsubshahere" or "This
> structure was never used and should be considered dead code"
> 
> I generally hope the intention of my commits is clear from the code with the
> commit log adding whatever context or elaboration on top.
> 
> So that's what I'm suggesting here. A bit of commit log sugar on top which
> elaborates on and justifies the change.

OK, so how about the version I suggested above:

 'reg_info' was never used since it's initial
 commit 5d0c3533a19f ("dmaengine: qcom: Add GPI dma driver")
 Remove it.

Is that OK with you?

Dave

> 
> ---
> bod
> 
-- 
 -----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   |_______/

  reply	other threads:[~2024-05-17 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 15:25 [PATCH v2] dmaengine: qcom: gpi: remove unused struct 'reg_info' linux
2024-05-17  9:11 ` Bryan O'Donoghue
2024-05-17 11:09   ` Dr. David Alan Gilbert
2024-05-17 11:19     ` Dr. David Alan Gilbert
2024-05-17 22:58       ` Bryan O'Donoghue
2024-05-17 23:04         ` Dr. David Alan Gilbert [this message]
2024-05-17 23:13           ` Bryan O'Donoghue
2024-05-17 23:41             ` Dr. David Alan Gilbert

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=Zkfidbh3Sqy6BEDh@gallifrey \
    --to=linux@treblig.org \
    --cc=Frank.li@nxp.com \
    --cc=bryan.odonoghue@linaro.org \
    --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 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.