public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Douglas Anderson <dianders@chromium.org>,
	Mike Leach <mike.leach@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH 0/5] coresight: Minor sparse and style fixes
Date: Mon, 27 Apr 2020 11:05:39 -0600	[thread overview]
Message-ID: <20200427170539.GC10601@xps15> (raw)
In-Reply-To: <20200426185805.14923-1-swboyd@chromium.org>

On Sun, Apr 26, 2020 at 11:58:00AM -0700, Stephen Boyd wrote:
> I got a report that kcalloc() didn't exist in coresight-cti-platform.c
> on arm builds and that looked like we didn't include very many headers
> to get prototypes of functions like kcalloc(), etc. The first patch fixes
> this problem by including the headers and then the rest of these
> patches fix minor sparse and style issues that I saw while looking
> through the coresight directory.
> 
> Pathes based on v5.7-rc1.
> 
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com> 
> Cc: Mike Leach <mike.leach@linaro.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> 
> Stephen Boyd (5):
>   coresight: Include required headers in C files
>   coresight: Mark some functions static
>   coresight: Don't initialize variables unnecessarily
>   coresight: Initialize arg in sparse friendly way
>   coresight: Avoid casting void pointers

I have applied patches 2, 3 and 4, so no need to send them again.  Note that I
dropped changes to coresight-cti.c and coresight-etb10.c in patch 2 as the
changes were already in my coresight-next branch.

Thanks,
Mathieu

> 
>  .../coresight/coresight-cti-platform.c          | 11 ++++++++---
>  .../hwtracing/coresight/coresight-cti-sysfs.c   | 17 ++++++++++++-----
>  drivers/hwtracing/coresight/coresight-cti.c     |  6 +++---
>  drivers/hwtracing/coresight/coresight-cti.h     | 10 +++++++++-
>  drivers/hwtracing/coresight/coresight-etb10.c   |  2 +-
>  drivers/hwtracing/coresight/coresight-etm3x.c   |  2 +-
>  drivers/hwtracing/coresight/coresight-etm4x.c   |  2 +-
>  .../hwtracing/coresight/coresight-platform.c    |  4 ++--
>  drivers/hwtracing/coresight/coresight-priv.h    |  9 ++++++---
>  drivers/hwtracing/coresight/coresight-tmc.c     |  2 +-
>  10 files changed, 44 insertions(+), 21 deletions(-)
> 
> 
> base-commit: 8f3d9f354286745c751374f5f1fcafee6b3f3136
> -- 
> Sent by a computer, using git, on the internet
> 

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

      parent reply	other threads:[~2020-04-27 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 18:58 [PATCH 0/5] coresight: Minor sparse and style fixes Stephen Boyd
2020-04-26 18:58 ` [PATCH 1/5] coresight: Include required headers in C files Stephen Boyd
2020-04-27 16:34   ` Mathieu Poirier
2020-04-28 17:34     ` Stephen Boyd
2020-04-26 18:58 ` [PATCH 2/5] coresight: Mark some functions static Stephen Boyd
2020-04-26 18:58 ` [PATCH 3/5] coresight: Don't initialize variables unnecessarily Stephen Boyd
2020-04-26 18:58 ` [PATCH 4/5] coresight: Initialize arg in sparse friendly way Stephen Boyd
2020-04-26 18:58 ` [PATCH 5/5] coresight: Avoid casting void pointers Stephen Boyd
2020-04-26 20:37   ` Joe Perches
2020-04-27 17:05 ` Mathieu Poirier [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=20200427170539.GC10601@xps15 \
    --to=mathieu.poirier@linaro.org \
    --cc=dianders@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=suzuki.poulose@arm.com \
    --cc=swboyd@chromium.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