linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	kernel-janitors@vger.kernel.org,
	 Julia Lawall <julia.lawall@lip6.fr>,
	Manivannan Sadhasivam <mani@kernel.org>,
	 "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	 "Martin K. Petersen" <martin.petersen@oracle.com>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	 linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH] scsi: ufs: qcom: Drop dead compile guard
Date: Tue, 5 Aug 2025 06:45:27 +0200	[thread overview]
Message-ID: <CAKXUXMzgABnN3bbV58xVwYNithcUg7fZgW0DxGCngJnNgNzrfw@mail.gmail.com> (raw)
In-Reply-To: <d7093377-a34e-4488-97c6-3d2ffcd13620@suswa.mountain>

On Fri, Aug 1, 2025 at 5:33 PM Dan Carpenter <dan.carpenter@linaro.org> wrote:
>
> This patch removes some dead ifdeffed code because the KConfig has a
> select which ensures that CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND is set.
> Konrad was wondering if there are any tools to detect this sort of
> thing.  I don't think so.  I think the only thing we detect are
> non-existant configs.  But let me add a few more people to the CC who
> might know.
>

I also have a simple script to search for unused configs, but that is
just five lines of bash and then a lot of manual filtering.

If I would attempt to implement such already rather complex analysis,
I would start with looking at this tool:

https://github.com/paulgazz/kmax

Possibly, there is a good way to re-use some parts of it or extend it
to look for the pattern above.

Lukas

> regards,
> dan carpenter
>
> On Thu, Jul 24, 2025 at 02:23:52PM +0200, Konrad Dybcio wrote:
> > From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> >
> > SCSI_UFSHCD already selects DEVFREQ_GOV_SIMPLE_ONDEMAND, drop the
> > check.
> >
> > Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> > ---
> > Is this something that could be discovered by our existing static
> > checkers?
> > ---
> >  drivers/ufs/host/ufs-qcom.c | 8 --------
> >  1 file changed, 8 deletions(-)
> >
> > diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
> > index 4bbe4de1679b908c85e6a3d4035fc9dcafcc0d1a..76fc70503a62eb2e747b2d4cd18cc05b6f5526c7 100644
> > --- a/drivers/ufs/host/ufs-qcom.c
> > +++ b/drivers/ufs/host/ufs-qcom.c
> > @@ -1898,7 +1898,6 @@ static int ufs_qcom_device_reset(struct ufs_hba *hba)
> >       return 0;
> >  }
> >
> > -#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
> >  static void ufs_qcom_config_scaling_param(struct ufs_hba *hba,
> >                                       struct devfreq_dev_profile *p,
> >                                       struct devfreq_simple_ondemand_data *d)
> > @@ -1910,13 +1909,6 @@ static void ufs_qcom_config_scaling_param(struct ufs_hba *hba,
> >
> >       hba->clk_scaling.suspend_on_no_request = true;
> >  }
> > -#else
> > -static void ufs_qcom_config_scaling_param(struct ufs_hba *hba,
> > -             struct devfreq_dev_profile *p,
> > -             struct devfreq_simple_ondemand_data *data)
> > -{
> > -}
> > -#endif
> >
> >  /* Resources */
> >  static const struct ufshcd_res_info ufs_res_info[RES_MAX] = {
> >
> > ---
> > base-commit: a933d3dc1968fcfb0ab72879ec304b1971ed1b9a
> > change-id: 20250724-topic-ufs_compile_check-3378996f4221
> >
> > Best regards,
> > --
> > Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

  reply	other threads:[~2025-08-05  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 12:23 [PATCH] scsi: ufs: qcom: Drop dead compile guard Konrad Dybcio
2025-07-24 14:19 ` Dmitry Baryshkov
2025-07-25  1:12 ` Martin K. Petersen
2025-08-01 15:33 ` Dan Carpenter
2025-08-05  4:45   ` Lukas Bulwahn [this message]
2025-08-05  7:04     ` Julia Lawall

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=CAKXUXMzgABnN3bbV58xVwYNithcUg7fZgW0DxGCngJnNgNzrfw@mail.gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dan.carpenter@linaro.org \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).