From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [RFC pve-kernel 2/2] update ABI file for 5.15.35-2-pve
Date: Tue, 31 May 2022 07:39:19 +0200 [thread overview]
Message-ID: <a854199a-5770-e444-0048-7e2b8238d50c@proxmox.com> (raw)
In-Reply-To: <20220530183848.2816971-3-s.ivanov@proxmox.com>
Am 30/05/2022 um 20:38 schrieb Stoiko Ivanov:
> (generated with debian/scripts/abi-generate)
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> abi-prev-5.15.35-1-pve | 26217 ---------------------------------------
> abi-prev-5.15.35-2-pve | 26209 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 26209 insertions(+), 26217 deletions(-)
> delete mode 100644 abi-prev-5.15.35-1-pve
> create mode 100644 abi-prev-5.15.35-2-pve
There's no need ever to send those huge, auto-generated diffs out over the mailing
list, especially if I only upload kernels I build myself and can generate and apply
the abi directly from those packages, if I forget it just ping me, as I cannot and
don't want to process such patches through the ML anyway. 3.6 MiB is far over the 80
KiB limit, always a good hint that something is off ;-)
prev parent reply other threads:[~2022-05-31 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 18:38 [pve-devel] [RFC pve-kernel 0/2] disable UBSAN in kernel config Stoiko Ivanov
2022-05-30 18:38 ` [pve-devel] [RFC pve-kernel 1/2] d/rules: kconfig: disable CONFIG_UBSAN Stoiko Ivanov
2022-05-30 18:38 ` [pve-devel] [RFC pve-kernel 2/2] update ABI file for 5.15.35-2-pve Stoiko Ivanov
2022-05-31 5:39 ` Thomas Lamprecht [this message]
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=a854199a-5770-e444-0048-7e2b8238d50c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.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