All of lore.kernel.org
 help / color / mirror / Atom feed
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: [PATCH 6.1 000/205] 6.1.134-rc2 review
Date: Thu, 10 Apr 2025 08:54:45 -0700	[thread overview]
Message-ID: <1744300485-11223-1-git-send-email-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20250409115832.610030955@linuxfoundation.org>

The kernel, bpf tool, perf tool, and kselftest builds fine for v6.1.134-rc2 on x86 and arm64 Azure VM.

Kernel binary size for x86 build:
text      data      bss      dec       hex      filename
25843965  11302730  16613376 53760071  3345047  vmlinux

Kernel binary size for arm64 build:
text      data      bss      dec       hex      filename
31254277  12542304  831088   44627669  2a8f6d5  vmlinux


Tested-by: Hardik Garg <hargar@linux.microsoft.com>




Thanks,
Hardik

  parent reply	other threads:[~2025-04-10 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 12:02 [PATCH 6.1 000/205] 6.1.134-rc2 review Greg Kroah-Hartman
2025-04-09 16:10 ` Miguel Ojeda
2025-04-09 20:25   ` Greg KH
2025-04-09 18:52 ` Shuah Khan
2025-04-09 20:14 ` Mark Brown
2025-04-09 20:31 ` Florian Fainelli
2025-04-10  2:46 ` Peter Schneider
2025-04-10  8:17 ` Naresh Kamboju
2025-04-10 12:08 ` Jon Hunter
2025-04-10 15:54 ` Hardik Garg [this message]
2025-04-11 14:29 ` Guenter Roeck
2025-04-22  8:51   ` 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=1744300485-11223-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.