All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"David Hildenbrand" <david@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org,
	qemu-s390x@nongnu.org
Subject: Re: [PATCH v5 0/3] linux-user: Allow gdbstub to ignore page protection
Date: Fri, 16 Feb 2024 13:36:05 +0100	[thread overview]
Message-ID: <a403dda185d7830f048aed8740bcf6c7ffeb3ac0.camel@linux.ibm.com> (raw)
In-Reply-To: <87h6i84os9.fsf@draig.linaro.org>

On Fri, 2024-02-16 at 11:44 +0000, Alex Bennée wrote:
> Ilya Leoshkevich <iii@linux.ibm.com> writes:
> 
> > v4:
> > https://lists.gnu.org/archive/html/qemu-devel/2024-01/msg05857.html
> > v4 -> v5: Fix the probe_proc_self_mem vs probe_proc_self_mem()
> > typo.
> >           Add Alex's R-b and A-b.
> 
> I was going to pull this and realised it already went in via
> Richard's
> tcg-next. Did this fix get merged?
> 

Hi, yes, I submitted it separately and it was merged as:

commit da4038d2da6d3a3d5f86665bd51b2ba49df5d652
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date:   Wed Jan 31 23:02:18 2024 +0100

    tests/tcg: Fix the /proc/self/mem probing in the PROT_NONE gdbstub
test


      reply	other threads:[~2024-02-16 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 11:46 [PATCH v5 0/3] linux-user: Allow gdbstub to ignore page protection Ilya Leoshkevich
2024-01-31 11:46 ` [PATCH v5 1/3] " Ilya Leoshkevich
2024-01-31 11:46 ` [PATCH v5 2/3] tests/tcg: Factor out gdbstub test functions Ilya Leoshkevich
2024-01-31 11:46 ` [PATCH v5 3/3] tests/tcg: Add the PROT_NONE gdbstub test Ilya Leoshkevich
2024-02-16 11:44 ` [PATCH v5 0/3] linux-user: Allow gdbstub to ignore page protection Alex Bennée
2024-02-16 12:36   ` Ilya Leoshkevich [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=a403dda185d7830f048aed8740bcf6c7ffeb3ac0.camel@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=david@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.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.