From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: James Clark <james.clark@arm.com>, coresight@lists.linaro.org
Cc: Mike Leach <mike.leach@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v3 0/4] coresight: Make current W=1 warnings default
Date: Fri, 12 Jan 2024 12:15:34 +0000 [thread overview]
Message-ID: <9856921b-40c4-4989-b7b6-134559564203@arm.com> (raw)
In-Reply-To: <20231123120459.287578-1-james.clark@arm.com>
On 23/11/2023 12:04, James Clark wrote:
> Changes since v2:
>
> * Split code and Makefile changes
> * Add a fix for a comment warning in etm3x
> * Add some sparse checker fixes in coresight-cfg-afdo.c
> * Fix the 0 instead of NULL warnings reported by kernel test robot
>
> James Clark (4):
> coresight: Fix uninitialized struct warnings
> coresight: etm3x: Fix build warning
> coresight: Fix undeclared variable warnings from sparse checker
> coresight: Make current W=1 warnings default
Apologies for the delay, this is now in my queue for next.
git://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git
for-next/queue
Suzuki
next prev parent reply other threads:[~2024-01-12 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 12:04 James Clark
2023-11-23 12:04 ` [PATCH v3 1/4] coresight: Fix uninitialized struct warnings James Clark
2023-11-23 12:04 ` [PATCH v3 2/4] coresight: etm3x: Fix build warning James Clark
2023-11-23 12:04 ` [PATCH v3 3/4] coresight: Fix undeclared variable warnings from sparse checker James Clark
2023-11-23 12:04 ` [PATCH v3 4/4] coresight: Make current W=1 warnings default James Clark
2024-01-12 12:15 ` Suzuki K Poulose [this message]
2024-02-12 11:27 ` [PATCH v3 0/4] " Suzuki K Poulose
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=9856921b-40c4-4989-b7b6-134559564203@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.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
all inboxes | Powered by JetHome®