public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org
Subject: Re: [PATCH 6.3 000/425] 6.3.13-rc2 review
Date: Mon, 10 Jul 2023 07:43:51 +0200	[thread overview]
Message-ID: <2023071039-puppet-wieldable-6db2@gregkh> (raw)
In-Reply-To: <CAEUSe7_KV_+jLJzE4u4_DHUPbi8Z=ASh-=aKB_JQr4+pz_8GVw@mail.gmail.com>

On Sun, Jul 09, 2023 at 04:55:55PM -0600, Daniel Díaz wrote:
> Hello!
> 
> On Sun, 9 Jul 2023 at 14:24, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > This is the start of the stable review cycle for the 6.3.13 release.
> > There are 425 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Tue, 11 Jul 2023 20:22:29 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> >         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.3.13-rc2.gz
> > or in the git tree and branch at:
> >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.3.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> This introduces a warning:
> -----8<-----
>   In file included from /builds/linux/block/genhd.c:28:
>   /builds/linux/block/genhd.c: In function 'disk_release':
>   /builds/linux/include/linux/blktrace_api.h:88:33: warning: statement
> with no effect [-Wunused-value]
>    # define blk_trace_remove(q)    (-ENOTTY)
>                                    ^
>   /builds/linux/block/genhd.c:1187:2: note: in expansion of macro
> 'blk_trace_remove'
>     blk_trace_remove(disk->queue);
>     ^~~~~~~~~~~~~~~~
> ----->8-----
> 
> This is again with Arm 32-bits on omap1_defconfig.
> 
> Bisection points to "block: fix blktrace debugfs entries leakage"
> (d8c9d0067dbd here, dd7de3704af9 upstream). Reverting this commit
> makes the warning go away.

Thanks, I've queued up a fix for this and will push out a -rc3.

greg k-h

      reply	other threads:[~2023-07-10  5:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09 20:24 [PATCH 6.3 000/425] 6.3.13-rc2 review Greg Kroah-Hartman
2023-07-09 22:55 ` Daniel Díaz
2023-07-10  5:43   ` Greg Kroah-Hartman [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=2023071039-puppet-wieldable-6db2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=conor@kernel.org \
    --cc=daniel.diaz@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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