mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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, allen.lkml@gmail.com, broonie@kernel.org,
	Vegard Nossum <vegard.nossum@oracle.com>,
	Darren Kenny <darren.kenny@oracle.com>
Subject: Re: [PATCH 5.15 000/691] 5.15.168-rc1 review
Date: Wed, 16 Oct 2024 14:52:19 +0530	[thread overview]
Message-ID: <b993840b-6610-43b2-a6d1-80d0bbd1286d@oracle.com> (raw)
In-Reply-To: <20241015112440.309539031@linuxfoundation.org>

Hi Greg,

On 15/10/24 16:49, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.168 release.
> There are 691 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.
> 

Like Florian we also see the build failure in perf/ and this is new from 
in this tag:

BUILDSTDERR: 
/builddir/build/BUILD/kernel-5.15.168/linux-5.15.168-master.20241015.el8.rc1/tools/perf/util/evsel.c: 
In function ‘evsel__set_count’:
BUILDSTDERR: 
/builddir/build/BUILD/kernel-5.15.168/linux-5.15.168-master.20241015.el8.rc1/tools/perf/util/evsel.c:1505:14: 
error: ‘struct perf_counts_values’ has no member named ‘lost’
BUILDSTDERR:  1505 |         count->lost   = lost;
BUILDSTDERR:       |              ^~

Thanks for dropping the commits pointed by Florian.


I am guessing we will have an rc2 soon, correct ?


Thanks,
Harshit


  parent reply	other threads:[~2024-10-16  9:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 11:19 Greg Kroah-Hartman
2024-10-15 11:28 ` [PATCH 5.15 560/691] arm64: Add Cortex-715 CPU part definition Greg Kroah-Hartman
2024-10-15 17:09 ` [PATCH 5.15 000/691] 5.15.168-rc1 review Florian Fainelli
2024-10-15 17:17   ` Greg Kroah-Hartman
2024-10-15 17:25     ` Florian Fainelli
2024-10-16  7:35       ` Greg Kroah-Hartman
2024-10-15 22:21 ` Shuah Khan
2024-10-16  8:54 ` Naresh Kamboju
2024-10-16  9:22 ` Harshit Mogalapalli [this message]
2024-10-16 10:01 ` Jon Hunter
2024-10-16 11:40 ` Ron Economos
2024-10-17 12:46 ` Muhammad Usama Anjum
2024-10-19 18:53 ` Guenter Roeck
2024-10-21  6:35   ` Michael Ellerman
2024-10-21  9:45     ` Greg Kroah-Hartman
2024-10-15 21:38 Richard Narron

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=b993840b-6610-43b2-a6d1-80d0bbd1286d@oracle.com \
    --to=harshit.m.mogalapalli@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=darren.kenny@oracle.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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 \
    --cc=vegard.nossum@oracle.com \
    /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®