From: Jakub Jelinek <jakub@redhat.com>
To: Costas Argyris <costas.argyris@gmail.com>
Cc: Jonathan Wakely <jwakely@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] driver: Fix memory leak.
Date: Fri, 8 Dec 2023 14:16:56 +0100 [thread overview]
Message-ID: <ZXMXSNQGQmjYT+OA@tucnak> (raw)
In-Reply-To: <CAHyHGCkeXFQNVmghuJ9ayb=rz02Yc=HcZXFTSXiqgAnNc97iGg@mail.gmail.com>
On Fri, Dec 08, 2023 at 12:18:50PM +0000, Costas Argyris wrote:
> Does the simple XDELETEVEC patch need any more work?
Well, it needs to be actually tested and posted and committed.
I can take care of it in my next bootstraps.
Jakub
prev parent reply other threads:[~2023-12-08 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 21:24 Costas Argyris
2023-12-04 12:15 ` Jonathan Wakely
2023-12-06 14:29 ` Costas Argyris
2023-12-06 14:39 ` Jakub Jelinek
2023-12-07 14:28 ` Costas Argyris
2023-12-07 14:42 ` Jakub Jelinek
2023-12-07 15:16 ` Costas Argyris
2023-12-07 15:42 ` Jakub Jelinek
2023-12-07 16:01 ` Costas Argyris
2023-12-07 16:04 ` Jakub Jelinek
2023-12-08 12:18 ` Costas Argyris
2023-12-08 13:16 ` Jakub Jelinek [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=ZXMXSNQGQmjYT+OA@tucnak \
--to=jakub@redhat.com \
--cc=costas.argyris@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.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).