CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Bryan Brattlof <bb@ti.com>,
	Daniel Wagner <daniel.wagner@monom.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	cip-dev@lists.cip-project.org,
	nobuhiro.iwamatsu.x90@mail.toshiba, pavel@nabladev.com,
	Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH 0/4] ARM: stable backports
Date: Mon, 22 Jun 2026 12:27:50 +0200	[thread overview]
Message-ID: <20260622102750.RMAlQTxT@linutronix.de> (raw)
In-Reply-To: <2026060832-extortion-cattail-2467@gregkh>

On 2026-06-08 16:12:05 [+0200], Greg KH wrote:
> We have hundreds of patches in the backlog right now, these are way down
> the list, sorry.  Hope to catch up "soon"...

No need to be sorry. Thank you (two) for doing the work.

> thanks,
> 
> greg k-h

Sebastian


      reply	other threads:[~2026-06-22 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 13:53 [PATCH 0/4] ARM: stable backports Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 1/4] ARM: group is_permission_fault() with is_translation_fault() Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 2/4] ARM: allow __do_kernel_fault() to report execution of memory faults Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 3/4] ARM: fix hash_name() fault Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 4/4] ARM: fix branch predictor hardening Sebastian Andrzej Siewior
2026-05-12  8:00 ` [PATCH 0/4] ARM: stable backports Pavel Machek
2026-05-13 13:51 ` Bryan Brattlof
2026-06-08  8:28 ` Sebastian Andrzej Siewior
2026-06-08 14:12   ` Greg KH
2026-06-22 10:27     ` Sebastian Andrzej Siewior [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=20260622102750.RMAlQTxT@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=bb@ti.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=daniel.wagner@monom.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jan.kiszka@siemens.com \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=pavel@nabladev.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=stable@vger.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