All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/3] scripts/coccinelle: New use-g_new-etc.cocci
Date: Mon, 14 Mar 2022 12:07:05 -0700	[thread overview]
Message-ID: <081a1629-6e5d-6835-b8be-435d23b90552@linaro.org> (raw)
In-Reply-To: <20220314160108.1440470-2-armbru@redhat.com>

On 3/14/22 09:01, Markus Armbruster wrote:
> This is the semantic patch from commit b45c03f585 "arm: Use g_new() &
> friends where that makes obvious sense".
> 
> Signed-off-by: Markus Armbruster<armbru@redhat.com>
> ---
>   scripts/coccinelle/use-g_new-etc.cocci | 75 ++++++++++++++++++++++++++
>   1 file changed, 75 insertions(+)
>   create mode 100644 scripts/coccinelle/use-g_new-etc.cocci

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

r~


  reply	other threads:[~2022-03-14 19:08 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 16:01 [PATCH 0/3] Use g_new() & friends where that makes obvious Markus Armbruster
2022-03-14 16:01 ` Markus Armbruster
2022-03-14 16:01 ` [PATCH 1/3] scripts/coccinelle: New use-g_new-etc.cocci Markus Armbruster
2022-03-14 16:01   ` Markus Armbruster
2022-03-14 19:07   ` Richard Henderson [this message]
2022-03-14 19:22   ` Alex Bennée
2022-03-14 19:22     ` Alex Bennée
2022-03-14 16:01 ` [PATCH 2/3] 9pfs: Use g_new() & friends where that makes obvious sense Markus Armbruster
2022-03-14 16:01   ` Markus Armbruster
2022-03-14 16:42   ` Christian Schoenebeck
2022-03-14 18:46     ` Philippe Mathieu-Daudé
2022-03-14 18:46       ` Philippe Mathieu-Daudé
2022-03-14 19:19       ` Christian Schoenebeck
2022-03-14 19:23   ` Alex Bennée
2022-03-14 19:23     ` Alex Bennée
2022-03-15  7:53   ` Greg Kurz
2022-03-15  7:53     ` Greg Kurz
2022-03-14 16:01 ` [PATCH 3/3] " Markus Armbruster
2022-03-14 16:01   ` Markus Armbruster
2022-03-14 16:08   ` Peter Maydell
2022-03-14 16:08     ` Peter Maydell
2022-03-14 16:52     ` Markus Armbruster
2022-03-14 16:52       ` Markus Armbruster
2022-03-14 17:39       ` Daniel P. Berrangé
2022-03-14 17:39         ` Daniel P. Berrangé
2022-03-14 17:06   ` Cédric Le Goater
2022-03-14 17:06     ` Cédric Le Goater
2022-03-14 19:48   ` Alex Bennée
2022-03-14 19:48     ` Alex Bennée
2022-03-14 20:37     ` Christian Schoenebeck
2022-03-15 13:49     ` Markus Armbruster
2022-03-15 13:49       ` Markus Armbruster
2022-03-14 22:52   ` Alex Bennée
2022-03-14 22:52     ` Alex Bennée
2022-03-15 13:59     ` Markus Armbruster
2022-03-15 13:59       ` Markus Armbruster
2022-03-15 14:07       ` Philippe Mathieu-Daudé
2022-03-15 14:07         ` Philippe Mathieu-Daudé
2022-03-15 14:43         ` Markus Armbruster
2022-03-15 14:43           ` Markus Armbruster
2022-03-15 16:16           ` Alex Bennée
2022-03-15 16:16             ` Alex Bennée
2022-03-15  9:07   ` Eric Blake
2022-03-15  9:07     ` Eric Blake
2022-03-15 14:03     ` Markus Armbruster
2022-03-15 14:03       ` Markus Armbruster
2022-03-15 10:58   ` Dr. David Alan Gilbert
2022-03-15 10:58     ` Dr. David Alan Gilbert
2022-03-14 16:41 ` [PATCH 0/3] Use g_new() & friends where that makes obvious Philippe Mathieu-Daudé
2022-03-14 16:41   ` Philippe Mathieu-Daudé

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=081a1629-6e5d-6835-b8be-435d23b90552@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.