From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Douglas Anderson <dianders@chromium.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>
Subject: Re: [PATCH v2 1/2] coresight: Include required headers in C files
Date: Mon, 4 May 2020 10:49:30 -0600 [thread overview]
Message-ID: <20200504164930.GA755@xps15> (raw)
In-Reply-To: <158852907765.11125.7786353455300506998@swboyd.mtv.corp.google.com>
On Sun, May 03, 2020 at 11:04:37AM -0700, Stephen Boyd wrote:
> Quoting Mathieu Poirier (2020-04-29 12:24:42)
> >
> > >
> > > So please remove slab.h from the two files (but not the other one) when
> > > applying. Thanks.
> >
> > You got it.
>
> I looked in next but coresight-cti-platform.c is missing slab.h even
> though I included it in my patch. There's a bare kcalloc() call in that
> file, so slab.h is required.
I know what happened. The above comment mentions removing slab.h in two and
leaving the "other" one in place. But looking at the original file only
coresight-cti-platform.c and coresight-cti-sysfs.c had an slab.h.
I have made the correction.
next prev parent reply other threads:[~2020-05-04 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 18:10 [PATCH v2 0/2] Minor sparse and style fixes Stephen Boyd
2020-04-28 18:10 ` [PATCH v2 1/2] coresight: Include required headers in C files Stephen Boyd
2020-04-29 18:08 ` Mathieu Poirier
2020-04-29 18:31 ` Stephen Boyd
2020-04-29 19:24 ` Mathieu Poirier
2020-05-03 18:04 ` Stephen Boyd
2020-05-04 16:49 ` Mathieu Poirier [this message]
2020-04-28 18:10 ` [PATCH v2 2/2] coresight: Avoid casting void pointers Stephen Boyd
2020-04-28 20:58 ` Mike Leach
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=20200504164930.GA755@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;
as well as URLs for NNTP newsgroup(s).