linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Nathan Chancellor <nathan@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
	James Clark <james.clark@arm.com>,
	coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coresight: cti: Remove unused variables in cti_{dis,en}able_hw()
Date: Mon, 24 Oct 2022 16:23:53 +0100	[thread overview]
Message-ID: <ad13afb6-a7d9-849b-b517-ab17d190b858@arm.com> (raw)
In-Reply-To: <20221024151201.2215380-1-nathan@kernel.org>

Hi Nathan

On 24/10/2022 16:12, Nathan Chancellor wrote:
> Clean up the following warnings, as the variables are no longer used.
> 
>    drivers/hwtracing/coresight/coresight-cti-core.c:93:17: warning: unused variable 'dev' [-Wunused-variable]
>            struct device *dev = &drvdata->csdev->dev;
>                          ^
>    drivers/hwtracing/coresight/coresight-cti-core.c:154:17: warning: unused variable 'dev' [-Wunused-variable]
>            struct device *dev = &drvdata->csdev->dev;
>                          ^
>    2 warnings generated.
> 
> Fixes: 665c157e0204 ("coresight: cti: Fix hang in cti_disable_hw()")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>

Thanks for your patch, this is now reverted upstream. I have
queued a patch locally to sqaush the changes and plan to push
it once the revert lands upstream.

Thanks
Suzuki


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-10-24 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 15:12 [PATCH] coresight: cti: Remove unused variables in cti_{dis,en}able_hw() Nathan Chancellor
2022-10-24 15:23 ` Suzuki K Poulose [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=ad13afb6-a7d9-849b-b517-ab17d190b858@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=coresight@lists.linaro.org \
    --cc=james.clark@arm.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=nathan@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;
as well as URLs for NNTP newsgroup(s).