stable-rt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: stable-rt <stable-rt@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Quick note about v5.10.199-rt97-rc1
Date: Fri, 3 Nov 2023 11:44:00 +0100	[thread overview]
Message-ID: <20231103104400.PWMC-z7p@linutronix.de> (raw)
In-Reply-To: <ZTnL6Maa9s9ZlETp@uudg.org>

On 2023-10-25 23:16:08 [-0300], Luis Claudio R. Goncalves wrote:
> Hello fellow maintainers!
> 
> I just pushed v5.10.199-rt97-rc1 (v5.10-rt-next) to kernel.org for testing.
> 
> The merge worked flawlessly but the build test failed with an undefined
> function. That was easy to track and fix, but I am not sure if the method
> I chose for the fix is the desired one.
> 
> In short, I performed the merge and then added the following patch to fix
> the build issue. Is this OK or should I have added this extra code in the
> merge?
> 
> Also, for the release, should I send the usual stable update message and
> add a note such as "the following change was required to fix a build
> problem: ..."?

Just looked at your v5.10.199-rt97-rc1 and considering everything it is
good. You could that a build failure was fixed due to upstream changes
affecting only the PREEMPT_RT part.

> Best regards,
> Luis

Sebastian

      parent reply	other threads:[~2023-11-03 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  2:16 Quick note about v5.10.199-rt97-rc1 Luis Claudio R. Goncalves
2023-10-26 13:12 ` Clark Williams
2023-11-03 10:44 ` 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=20231103104400.PWMC-z7p@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=lgoncalv@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stable-rt@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).