From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: Sergei Trofimovich <siarheit@google.com>,
gdb-patches@sourceware.org,
M R Swami Reddy <MR.Swami.Reddy@nsc.com>
Subject: Re: [PATCH] cr16: fix build on gcc-12 (NULL comparison)
Date: Sun, 14 Nov 2021 21:45:35 -0500 [thread overview]
Message-ID: <YZHJz2lO0HSrW5ea@vapier> (raw)
In-Reply-To: <20211114183556.3460823-1-slyich@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 19 bytes --]
lgtm, thanks
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-11-15 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 18:35 Sergei Trofimovich via Gdb-patches
2021-11-15 2:45 ` Mike Frysinger via Gdb-patches [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=YZHJz2lO0HSrW5ea@vapier \
--to=gdb-patches@sourceware.org \
--cc=MR.Swami.Reddy@nsc.com \
--cc=siarheit@google.com \
--cc=slyich@gmail.com \
--cc=vapier@gentoo.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