linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	linux-kernel@vger.kernel.org, stable@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,
	slade@sladewatkins.com, Paulo Alcantara <pc@cjr.nz>,
	Enzo Matsumiya <ematsumiya@suse.de>,
	Steve French <stfrench@microsoft.com>
Subject: Re: [PATCH 5.18 0/6] 5.18.9-rc1 review
Date: Mon, 4 Jul 2022 16:40:16 +0200	[thread overview]
Message-ID: <YsL70A0fxJ6BtwDu@kroah.com> (raw)
In-Reply-To: <Yr7M//9X8RdNz+Hu@debian>

On Fri, Jul 01, 2022 at 11:31:27AM +0100, Sudip Mukherjee wrote:
> On Fri, Jul 01, 2022 at 10:24:10AM +0200, Greg Kroah-Hartman wrote:
> > On Fri, Jul 01, 2022 at 02:59:10PM +0700, Bagas Sanjaya wrote:
> > > On Thu, Jun 30, 2022 at 03:47:26PM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 5.18.9 release.
> > > > There are 6 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.
> > > > 
> > > 
> > > Successfully cross-compiled for arm64 (bcm2711_defconfig, GCC 12.1.0)
> > > and powerpc (ps3_defconfig, GCC 12.1.0).
> > > 
> > > I get a warning on cifs:
> > > 
> > >   CC [M]  fs/cifs/connect.o
> > >   CC      drivers/tty/tty_baudrate.o
> > >   CC      drivers/tty/tty_jobctrl.o
> > > fs/cifs/connect.c: In function 'is_path_remote':
> > > fs/cifs/connect.c:3426:14: warning: unused variable 'nodfs' [-Wunused-variable]
> > >  3426 |         bool nodfs = cifs_sb->mnt_cifs_flags & CIFS_MOUNT_NO_DFS;
> > >       |              ^~~~~
> > > 
> > > The culprit is commit 2340f1adf9fbb3 ("cifs: don't call
> > > cifs_dfs_query_info_nonascii_quirk() if nodfs was set") (upstream commit
> > > 421ef3d56513b2).
> > 
> > Again, gcc-12 is going to have problems with stable releases until
> > Linus's tree is fixed up entirely.  Once that happens, then I will take
> > backports to stable kernels to get them to build properly.
> 
> I have not tested, but this should be fixed by this one:
> 
> 93ed91c020aa ("cifs: fix minor compile warning")

Thanks, now queued up.

greg k-h

  reply	other threads:[~2022-07-04 14:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 13:47 [PATCH 5.18 0/6] 5.18.9-rc1 review Greg Kroah-Hartman
2022-06-30 13:47 ` [PATCH 5.18 1/6] tick/nohz: unexport __init-annotated tick_nohz_full_setup() Greg Kroah-Hartman
2022-06-30 13:47 ` [PATCH 5.18 2/6] clocksource/drivers/ixp4xx: Drop boardfile probe path Greg Kroah-Hartman
2022-06-30 13:47 ` [PATCH 5.18 3/6] bcache: memset on stack variables in bch_btree_check() and bch_sectors_dirty_init() Greg Kroah-Hartman
2022-06-30 13:47 ` [PATCH 5.18 4/6] hinic: Replace memcpy() with direct assignment Greg Kroah-Hartman
2022-06-30 13:47 ` [PATCH 5.18 5/6] powerpc/ftrace: Remove ftrace init tramp once kernel init is complete Greg Kroah-Hartman
2022-06-30 13:47 ` [PATCH 5.18 6/6] io_uring: fix not locked access to fixed buf table Greg Kroah-Hartman
2022-06-30 22:35 ` [PATCH 5.18 0/6] 5.18.9-rc1 review Zan Aziz
2022-06-30 23:19 ` Shuah Khan
2022-06-30 23:46 ` Florian Fainelli
2022-07-01  0:58 ` Guenter Roeck
2022-07-01  4:17 ` Ron Economos
2022-07-01  5:59 ` Naresh Kamboju
2022-07-01  7:59 ` Bagas Sanjaya
2022-07-01  8:24   ` Greg Kroah-Hartman
2022-07-01  9:00     ` Bagas Sanjaya
2022-07-01 10:31     ` Sudip Mukherjee
2022-07-04 14:40       ` Greg Kroah-Hartman [this message]
2022-07-01 10:25 ` Sudip Mukherjee
2022-07-01 11:53 ` Rudi Heitbaum
2022-07-01 11:56 ` Rudi Heitbaum
2022-07-01 17:45 ` Justin Forbes
2022-06-30 15:30 Ronald Warsow

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=YsL70A0fxJ6BtwDu@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bagasdotme@gmail.com \
    --cc=ematsumiya@suse.de \
    --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=pavel@denx.de \
    --cc=pc@cjr.nz \
    --cc=shuah@kernel.org \
    --cc=slade@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=stfrench@microsoft.com \
    --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;
as well as URLs for NNTP newsgroup(s).