From: Hardik Garg <hargar@linux.microsoft.com>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
lkft-triage@lists.linaro.org, patches@kernelci.org,
patches@lists.linux.dev, pavel@denx.de, rwarsow@gmx.de,
shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.15 000/780] 6.15.3-rc1 review
Date: Wed, 18 Jun 2025 11:07:40 -0700 [thread overview]
Message-ID: <1750270060-30222-1-git-send-email-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20250617152451.485330293@linuxfoundation.org>
The kernel, bpf tool, and perf tool builds fine for v6.15.3-rc1 on x86 and arm64 Azure VM.
Kernel binary size for x86 build:
text data bss dec hex filename
31998596 14275846 6250496 52524938 321778a vmlinux
Kernel binary size for arm64 build:
text data bss dec hex filename
37335273 15435305 1038736 53809314 33510a2 vmlinux
Tested-by: Hardik Garg <hargar@linux.microsoft.com>
Thanks,
Hardik
next prev parent reply other threads:[~2025-06-18 18:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:15 [PATCH 6.15 000/780] 6.15.3-rc1 review Greg Kroah-Hartman
2025-06-17 15:22 ` [PATCH 6.15 468/780] perf symbol: Fix use-after-free in filename__read_build_id Greg Kroah-Hartman
2025-06-17 16:12 ` [PATCH 6.15 000/780] 6.15.3-rc1 review Christian Heusel
2025-06-17 16:49 ` Florian Fainelli
2025-06-17 18:27 ` Ronald Warsow
2025-06-17 21:10 ` Luna Jernberg
2025-06-18 5:42 ` Greg Kroah-Hartman
2025-06-18 13:32 ` Pascal Ernster
[not found] ` <20250617152521.879529420@linuxfoundation.org>
[not found] ` <04b7faf5-2f69-4d02-9eca-916e4bffcf00@gmx.de>
2025-06-18 19:58 ` Pascal Ernster
2025-06-18 20:31 ` Pascal Ernster
2025-06-19 4:17 ` Greg Kroah-Hartman
2025-06-21 22:09 ` Pascal Ernster
2025-06-22 7:24 ` Greg Kroah-Hartman
2025-06-17 21:17 ` Shuah Khan
2025-06-18 5:51 ` Achill Gilgenast
2025-06-18 6:19 ` Ron Economos
2025-06-18 6:42 ` Jon Hunter
2025-06-18 8:11 ` Takeshi Ogasawara
2025-06-18 8:35 ` Peter Schneider
2025-06-18 10:38 ` Naresh Kamboju
2025-06-18 11:58 ` Mark Brown
2025-06-18 13:19 ` Greg Kroah-Hartman
2025-06-18 14:15 ` Thomas Weißschuh
2025-06-19 4:19 ` Greg Kroah-Hartman
2025-06-19 5:50 ` Thomas Weißschuh
2025-06-19 8:20 ` Greg Kroah-Hartman
2025-06-18 12:59 ` Miguel Ojeda
2025-06-18 18:07 ` Hardik Garg [this message]
2025-06-19 1:36 ` Justin Forbes
2025-06-19 4:05 ` Greg Kroah-Hartman
2025-06-19 4:06 ` Greg Kroah-Hartman
2025-06-23 21:05 ` Naresh Kamboju
2025-06-24 10:15 ` Greg Kroah-Hartman
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=1750270060-30222-1-git-send-email-hargar@linux.microsoft.com \
--to=hargar@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.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;
as well as URLs for NNTP newsgroup(s).