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.1 000/569] 6.1.129-rc2 review
Date: Thu, 20 Feb 2025 10:01:17 -0800 [thread overview]
Message-ID: <1740074477-27449-1-git-send-email-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20250220104545.805660879@linuxfoundation.org>
The kernel, bpf tool, perf tool, and kselftest builds fine for v6.1.129-rc2 on x86 and arm64 Azure VM.
Kernel binary size for x86 build:
text data bss dec hex filename
25841866 11293522 16617472 53752860 334341c vmlinux
Kernel binary size for arm64 build:
text data bss dec hex filename
31262891 12537932 831144 44631967 2a9079f vmlinux
Tested-by: Hardik Garg <hargar@linux.microsoft.com>
Thanks,
Hardik
next prev parent reply other threads:[~2025-02-20 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 10:57 [PATCH 6.1 000/569] 6.1.129-rc2 review Greg Kroah-Hartman
2025-02-20 13:51 ` Mark Brown
2025-02-20 18:01 ` Hardik Garg [this message]
2025-02-20 19:57 ` Pavel Machek
2025-02-20 20:45 ` Slade Watkins
2025-02-21 11:04 ` Peter Schneider
2025-02-21 11:53 ` Jon Hunter
2025-02-21 17:45 ` Florian Fainelli
2025-02-22 6:28 ` Greg Kroah-Hartman
2025-02-22 9:21 ` Pavel Machek
2025-02-22 9:39 ` Greg Kroah-Hartman
2025-02-22 9:46 ` Pavel Machek
2025-05-12 9:21 ` Pavel Machek
2025-05-12 9:31 ` Greg Kroah-Hartman
2025-05-12 9:55 ` Pavel Machek
2025-02-24 8:10 ` Naresh Kamboju
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=1740074477-27449-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.