From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix for v850e divq instruction
Date: Tue, 5 Apr 2022 23:56:17 -0400 [thread overview]
Message-ID: <Yk0PYeS4mi3Emn0C@vapier> (raw)
In-Reply-To: <e22d76f5-6343-3e86-1713-d6a05112a0bc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 93 bytes --]
seems fine (assuming you included your extended explanation in the git
commit message)
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-04-06 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4eaa501f-9b0a-20dc-6972-0ca0686d2a75@gmail.com>
2022-04-04 22:49 ` Fwd: " Jeff Law via Gdb-patches
2022-04-06 3:56 ` 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=Yk0PYeS4mi3Emn0C@vapier \
--to=gdb-patches@sourceware.org \
--cc=jeffreyalaw@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