public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	jstultz@google.com, Stephen Boyd <sboyd@kernel.org>
Subject: Re: Patch "timekeeping: Fix possible inconsistencies in _COARSE clockids" has been added to the 6.14-stable tree
Date: Mon, 7 Apr 2025 21:09:43 -0400	[thread overview]
Message-ID: <Z_R3V-sJDh_VWryx@lappy> (raw)
In-Reply-To: <87zfgsujs5.ffs@tglx>

On Mon, Apr 07, 2025 at 04:29:46PM +0200, Thomas Gleixner wrote:
>On Mon, Apr 07 2025 at 10:07, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>>     timekeeping: Fix possible inconsistencies in _COARSE clockids
>>
>> to the 6.14-stable tree which can be found at:
>>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>>      timekeeping-fix-possible-inconsistencies-in-_coarse-.patch
>> and it can be found in the queue-6.14 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>
>As I asked on the stable list already, please do not add that to any
>stable tree. It has been reverted in Linus tree and the problem will be
>fixed differently.

Sorry about this, now dropped.

-- 
Thanks,
Sasha

      reply	other threads:[~2025-04-08  1:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250407140759.3092465-1-sashal@kernel.org>
2025-04-07 14:29 ` Patch "timekeeping: Fix possible inconsistencies in _COARSE clockids" has been added to the 6.14-stable tree Thomas Gleixner
2025-04-08  1:09   ` Sasha Levin [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=Z_R3V-sJDh_VWryx@lappy \
    --to=sashal@kernel.org \
    --cc=jstultz@google.com \
    --cc=sboyd@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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