From: Milan Oravec <moravec@ukf.sk>
To: Marco Scardovi <scardracs@disroot.org>
Cc: bp@alien8.de, crecklin@redhat.com, dave.hansen@linux.intel.com,
hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, mingo@redhat.com, pavel@kernel.org,
rafael@kernel.org, regressions@leemhuis.info,
regressions@lists.linux.dev, tglx@kernel.org, x86@kernel.org
Subject: Re: [PATCH v2 0/4] PM: hibernate: Add relaxed_memmap option for x86 E820 integrity check
Date: Tue, 30 Jun 2026 08:52:28 +0200 [thread overview]
Message-ID: <10a377de-b0f2-4b99-ba2a-32e70dac2ebf@ukf.sk> (raw)
In-Reply-To: <2_MjK2gjTYawu-VEuCwZxw@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]
Hello Marco, thank you for your effort and help. Unfortunately no
solution for my system. :(
Best regards,
Milan
s pozdravom
Milan Oravec
CIKT UKF Nitra
Mobil/Signal: +421907670270
email: moravec@ukf.sk
--------------------------------------------------------------------
Tuto spravu nepreveril ziadny antivirus - nebolo treba...
On 6/29/26 21:53, Marco Scardovi wrote:
> In data lunedì 29 giugno 2026 15:04:04 Ora legale dell’Europa centrale, Milan Oravec ha scritto:
>> Hello, I wanted to try this new set of patches, but I was unable to
>> apply them. Tested with 7.1.2 and master too.
>>
>> migo@migo-HP:~/build/linux-test/linux$ patch -p1 < ../hibernate2.patch
>> patching file include/linux/suspend.h
>> patching file kernel/power/hibernate.c
>> Hunk #2 FAILED at 1431.
>> 1 out of 2 hunks FAILED -- saving rejects to file
>> kernel/power/hibernate.c.rej
>> patching file arch/x86/power/hibernate.c
>> Hunk #1 FAILED at 61.
>> Hunk #2 succeeded at 78 with fuzz 1.
>> Hunk #3 FAILED at 144.
>> Hunk #4 FAILED at 166.
>> 3 out of 4 hunks FAILED -- saving rejects to file
>> arch/x86/power/hibernate.c.rej
>> patching file Documentation/admin-guide/kernel-parameters.txt
>> Hunk #1 FAILED at 1967.
>> 1 out of 1 hunk FAILED -- saving rejects to file
>> Documentation/admin-guide/kernel-parameters.txt.rej
>>
>> Thank you,
>>
>> Milan
>>
> Hi Milan,
> that's probably because all the patches I write are against linux-next and
> not a specific linux version. In that case linux-next contain [1] which
> is not on stable version, making the patch non working for you.
>
> To be honest I'm not gonna release a new patch specifically for kernel 7.1:
> it's a waste of effort to target a specific version as the patch will be merged
> (if rafael will agree with it) in a future version. Said that, I'm not even
> sure it will be merged for the points stated by Rafael, which I understand
> and agree.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/kernel/power/hibernate.c?h=next-20260629&id=783c8109844503bd1c35dab41b6d5fd074a9f131
>
> With best regards,
> Marco
>
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4983 bytes --]
prev parent reply other threads:[~2026-06-30 6:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 8:15 [PATCH 0/1] x86/power: only verify usable RAM regions during hibernation E820 check Marco Scardovi
2026-06-20 8:15 ` [PATCH 1/1] " Marco Scardovi
2026-06-20 9:20 ` Milan Oravec
2026-06-23 12:59 ` Rafael J. Wysocki
2026-06-23 15:11 ` Milan Oravec
2026-06-23 16:47 ` [PATCH v2 0/4] PM: hibernate: Add relaxed_memmap option for x86 E820 integrity check Marco Scardovi
2026-06-23 16:47 ` [PATCH v2 1/4] PM: hibernate: Declare hibernate_relaxed_memmap Marco Scardovi
2026-06-23 16:47 ` [PATCH v2 2/4] PM: hibernate: Define and parse hibernate=relaxed_memmap parameter Marco Scardovi
2026-06-23 16:47 ` [PATCH v2 3/4] x86/power: Implement relaxed E820 memory map integrity check Marco Scardovi
2026-06-23 16:47 ` [PATCH v2 4/4] Documentation: Document hibernate=relaxed_memmap parameter option Marco Scardovi
2026-06-29 13:04 ` [PATCH v2 0/4] PM: hibernate: Add relaxed_memmap option for x86 E820 integrity check Milan Oravec
2026-06-29 19:53 ` Marco Scardovi
2026-06-30 6:52 ` Milan Oravec [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=10a377de-b0f2-4b99-ba2a-32e70dac2ebf@ukf.sk \
--to=moravec@ukf.sk \
--cc=bp@alien8.de \
--cc=crecklin@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=scardracs@disroot.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®