From: Nick Clifton <nickc@redhat.com>
To: Nick Alcock <nick.alcock@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH 2.40 v2 3/3] libctf: ctf-link outdated input check faulty
Date: Thu, 12 Jan 2023 13:43:15 +0000 [thread overview]
Message-ID: <7c1372ff-47c4-5e4e-cc16-73a300078de1@redhat.com> (raw)
In-Reply-To: <87r0w1oulw.fsf_-_@esperi.org.uk>
Hi Nick,
> Is this patch alone OK for 2.40?
It is - but please do this today if you can - I am planning on creating
the release tarballs tomorrow...
> (After I push this series to master.
> Tomorrow, not today... all tests passed, crash on i686-pc-linux-gnu
> fixed, valgrind-clean, asan-clean.)
>
> (I plan to backport it all the way back to 2.36.)
Have fun!
Cheers
Nick
next prev parent reply other threads:[~2023-01-12 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 13:00 [PATCH v2 0/3] A few backlogged fixes, and a crash bug Nick Alcock
2023-01-10 13:00 ` [PATCH v2 1/3] ctf: fix various dreadful typos in the ctf_archive format comments Nick Alcock
2023-01-10 13:00 ` [PATCH v2 2/3] libctf: skip the testsuite from inside dejagnu Nick Alcock
2023-01-10 13:00 ` [PATCH v2 3/3] libctf: ctf-link outdated input check faulty Nick Alcock
2023-01-11 17:21 ` [PATCH 2.40 " Nick Alcock
2023-01-12 13:43 ` Nick Clifton [this message]
2023-01-12 14:46 ` Nick Alcock
2023-01-12 15:39 ` Nick Alcock
2023-01-13 11:14 ` Nick Clifton
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=7c1372ff-47c4-5e4e-cc16-73a300078de1@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=nick.alcock@oracle.com \
/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).