public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Rajendra SY <rajendra.sy@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [PR gdb/23077] Fix error 'Couldn't get registers: Device busy' on FreeBSD
Date: Fri, 20 Apr 2018 09:45:00 -0000	[thread overview]
Message-ID: <575fee2c-b0ac-6843-63de-4b36c29c1f12@redhat.com> (raw)
In-Reply-To: <CAMAnt0k9PSCe-J+CNbq3PLWL50zOB9mcWazDJS-tnWrNkyjtBQ@mail.gmail.com>

Hi!

FYI, your emails are missing the actual patches:

 https://sourceware.org/ml/gdb-patches/2018-04/msg00396.html
 https://sourceware.org/ml/gdb-patches/2018-04/msg00397.html

Thanks,
Pedro Alves

  reply	other threads:[~2018-04-20  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20  9:38 Rajendra SY
2018-04-20  9:45 ` Pedro Alves [this message]
2018-04-20  9:46 Rajendra SY
2018-04-20 13:32 ` Pedro Alves
2018-04-20 15:19   ` Rajendra SY

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=575fee2c-b0ac-6843-63de-4b36c29c1f12@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=rajendra.sy@gmail.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).