All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 Baoquan He <baoquan.he@linux.dev>,
	 Pasha Tatashin <pasha.tatashin@soleen.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	 Dave Young <ruirui.yang@linux.dev>,  Coiby Xu <coxu@redhat.com>,
	kexec@lists.infradead.org,  linux-kernel@vger.kernel.org,
	 Guangshuo Li <lgs201920130244@gmail.com>
Subject: Re: [PATCH v2] crash_dump: release keyring reference at the correct time
Date: Mon, 13 Jul 2026 14:41:06 +0200	[thread overview]
Message-ID: <2vxz7bmzkqot.fsf@kernel.org> (raw)
In-Reply-To: <178392639372.255896.15219634537212682820.b4-ty@b4> (Mike Rapoport's message of "Mon, 13 Jul 2026 10:06:33 +0300")

Hi Mike,

On Mon, Jul 13 2026, Mike Rapoport wrote:

> On Sat, 04 Jul 2026 19:25:09 +0800, Guangshuo Li wrote:
>> crash_dump: release keyring reference at the correct time
>
> Applied to kexec-fixes branch of liveupdate/linux.git tree, thanks!
>
> [1/1] crash_dump: release keyring reference at the correct time
>       commit: ada2e5a44e99113e08ad9b7b71396c6c572204da
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux
> branch: kexec-fixes

For me kexec-fixes points to v7.2-rc1 still. Did you forget to push?

-- 
Regards,
Pratyush Yadav


  reply	other threads:[~2026-07-13 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04 11:25 [PATCH v2] crash_dump: release keyring reference at the correct time Guangshuo Li
2026-07-06  2:59 ` Coiby Xu
2026-07-12 12:00 ` Baoquan He
2026-07-12 12:02   ` Bradley Morgan
2026-07-13  7:06 ` Mike Rapoport
2026-07-13 12:41   ` Pratyush Yadav [this message]
2026-07-13 13:30     ` Mike Rapoport

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=2vxz7bmzkqot.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baoquan.he@linux.dev \
    --cc=coxu@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=lgs201920130244@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=rppt@kernel.org \
    --cc=ruirui.yang@linux.dev \
    /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.