[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190703155849.GA19567@kroah.com>
Date: Wed, 3 Jul 2019 17:58:49 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org,
Shaokun Zhang <zhangshaokun@...ilicon.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [GIT PULL 1/9] intel_th: msu: Fix unused variable warning on
arm64 platform
On Wed, Jul 03, 2019 at 06:54:05PM +0300, Alexander Shishkin wrote:
> Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
>
> > On Thu, Jun 27, 2019 at 03:51:44PM +0300, Alexander Shishkin wrote:
> >> From: Shaokun Zhang <zhangshaokun@...ilicon.com>
> >>
> >> Commit ba39bd8306057 ("intel_th: msu: Switch over to scatterlist")
> >> introduced the following warnings on non-x86 architectures, as a result
> >> of reordering the multi mode buffer allocation sequence:
> >>
> >> > drivers/hwtracing/intel_th/msu.c: In function ‘msc_buffer_win_alloc’:
> >> > drivers/hwtracing/intel_th/msu.c:783:21: warning: unused variable ‘i’
> >> > [-Wunused-variable]
> >> > int ret = -ENOMEM, i;
> >> > ^
> >> > drivers/hwtracing/intel_th/msu.c: In function ‘msc_buffer_win_free’:
> >> > drivers/hwtracing/intel_th/msu.c:863:6: warning: unused variable ‘i’
> >> > [-Wunused-variable]
> >> > int i;
> >> > ^
> >>
> >> Fix this compiler warning by factoring out set_memory sequences and making
> >> them x86-only.
> >>
> >> Suggested-by: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
> >> Signed-off-by: Shaokun Zhang <zhangshaokun@...ilicon.com>
> >> Fixes: ba39bd8306057 ("intel_th: msu: Switch over to scatterlist")
> >> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> >> Signed-off-by: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
> >> ---
> >> drivers/hwtracing/intel_th/msu.c | 40 +++++++++++++++++++++-----------
> >> 1 file changed, 27 insertions(+), 13 deletions(-)
> >
> > Does not apply to my tree :(
>
> It's the same one as the one in the fixes series. I just put it here for
> completeness.
to be extra sure it was really applied? that's funny...
Powered by blists - more mailing lists