mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, 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.1 000/127] 6.1.45-rc1 review
Date: Fri, 11 Aug 2023 12:06:16 +0200	[thread overview]
Message-ID: <2023081105-gentleman-greyhound-75c4@gregkh> (raw)
In-Reply-To: <fcd7b764-9047-22ba-a040-41b6ff99959c@roeck-us.net>

On Thu, Aug 10, 2023 at 03:15:28AM -0700, Guenter Roeck wrote:
> On 8/9/23 03:39, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.45 release.
> > There are 127 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 Fri, 11 Aug 2023 10:36:10 +0000.
> > Anything received after that time might be too late.
> > 
> 
> 
> Building loongarch:defconfig ... failed
> --------------
> Error log:
> <stdin>:569:2: warning: #warning syscall fstat not implemented [-Wcpp]
> arch/loongarch/kernel/setup.c: In function 'arch_cpu_finalize_init':
> arch/loongarch/kernel/setup.c:86:9: error: implicit declaration of function 'alternative_instructions'
> 
> Actually introduced in v6.1.44 with commit 08e86d42e2c9 ("loongarch/cpu:
> Switch to arch_cpu_finalize_init()"). Alternative instruction support
> was only introduced for loongarch in v6.2 with commit 19e5eb15b00c
> ("LoongArch: Add alternative runtime patching mechanism").

Thanks for the report, I'll fix this after this release.

greg k-h

  reply	other threads:[~2023-08-11 10:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 10:39 Greg Kroah-Hartman
2023-08-09 13:42 ` Joel Fernandes
2023-08-09 17:08 ` SeongJae Park
2023-08-09 21:38 ` Florian Fainelli
2023-08-10  3:54 ` Bagas Sanjaya
2023-08-10  5:12 ` Takeshi Ogasawara
2023-08-10  7:06 ` Ron Economos
2023-08-10 10:15 ` Guenter Roeck
2023-08-11 10:06   ` Greg Kroah-Hartman [this message]
2023-08-10 10:28 ` Conor Dooley
2023-08-10 16:14 ` Guenter Roeck
2023-08-11 10:07   ` Greg Kroah-Hartman
2023-08-11 10:26     ` Guenter Roeck
2023-08-10 21:17 ` Miguel Ojeda
2023-08-11  3:22 ` Naresh Kamboju
2023-08-11  3:36   ` Nathan Chancellor
2023-08-11  3:41   ` Guenter Roeck
2023-08-11  4:13     ` Nathan Chancellor
2023-08-13 11:02       ` Borislav Petkov
2023-08-14 16:52         ` Nathan Chancellor
2023-08-14 11:17 ` Thierry Reding
2023-08-14 12:58 ` Conor Dooley

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=2023081105-gentleman-greyhound-75c4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=conor@kernel.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

all inboxes | Powered by JetHome®