From: Sasha Levin <sashal@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: stable-commits@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Patch "ring-buffer: Force absolute timestamp on discard of event" has been added to the 6.1-stable tree
Date: Sun, 31 Dec 2023 10:42:52 -0500 [thread overview]
Message-ID: <ZZGL_COQ_bo-dnEy@sashalap> (raw)
In-Reply-To: <20231230112246.72c8b2cd@gandalf.local.home>
Hey Steve,
On Sat, Dec 30, 2023 at 11:22:46AM -0500, Steven Rostedt wrote:
>
>Sasha,
>
>Was this automated or did you do this manually?
This is mostly automated.
>I'm asking because I was walking through my INBOX to see what FAILED
>backports I could clean up, and I started on this one:
>
> https://lore.kernel.org/all/2023120938-unclamped-fleshy-688e@gregkh/
>
>I did the cherry pick, fixed up the conflict, but when I tried to commit
>it, it failed because there was nothing to commit.
>
>This confused me for a bit, and then when I did a git blame, I saw that you
>had done the fix already.
>
>When you fix a FAILED patch, can you do a reply to the FAILED message that
>Greg sends out, so that I don't waste my time on trying to fix something
>that was already fixed?
The process I have is that I go over the stable tagged commits with a
week or two delay, and attempt to apply the commits that aren't in the
tree yet using the dependency bot.
I can look into how to tie this into Greg's FAILED emails; I used to do
the above manually and reply to those mails, but now the process is
slightly different and there's no direct connection between the two.
--
Thanks,
Sasha
prev parent reply other threads:[~2023-12-31 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231210194035.164923-1-sashal@kernel.org>
2023-12-30 16:22 ` Patch "ring-buffer: Force absolute timestamp on discard of event" has been added to the 6.1-stable tree Steven Rostedt
2023-12-31 15:42 ` 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=ZZGL_COQ_bo-dnEy@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable-commits@vger.kernel.org \
--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