public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Christophe Lyon <christophe.lyon@arm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Maxim Kuvyrkov via Gdb-patches <gdb-patches@sourceware.org>,
	torbjorn.svensson@st.com, Yvan Roux <yvan.roux@linaro.org>,
	Luis Machado <Luis.Machado@arm.com>
Subject: Re: [PATCH v3 0/5] arm: Add support for multiple stacks on Cortex-M
Date: Sun, 6 Mar 2022 14:48:12 +0400	[thread overview]
Message-ID: <YiSRbD7kpzC+SrZr@adacore.com> (raw)
In-Reply-To: <c3b36fa7-b688-3689-a49e-89a92bb7d076@arm.com>

> > > Will you be able to review this patch series from Christophe?
> > I see that the v3 series was posted on Feb 4th, while on Feb 6th
> > I reviewed v2 :-(. This is really unfortunate that we don't have
> > a better system for tracking whether a version of a series is
> > trully the latest version.
> 
> No problem, there's not much difference between v2 and v3,
> so your comments still apply. I should have answered earlier.
> 
> > 
> > Can you take a look at the comments and question I asked in v2,
> > and publish a v4 which takes those into account? Please Cc: me
> > on the submission of the patches, this will help me remember
> > to prioritize those patches.
> 
> 
> Sure!
> 
> Luis and I changed jobs at the same time, so there's a bit
> of lag :-)

No problem!

Just for the avoidance of doubt and you don't end up waiting on me,
my understanding is that the next step is for you to produce a v4
with some of my comments addressed, and to post answers/questions
for my comments. Is that right?

-- 
Joel

  reply	other threads:[~2022-03-06 10:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04  8:41 christophe.lyon.oss
2022-02-04  8:41 ` [PATCH v3 1/5] gdb/arm: Fix prologue analysis to support vpush christophe.lyon.oss
2022-02-04  8:41 ` [PATCH v3 2/5] gdb/arm: Define MSP and PSP registers for M-Profile christophe.lyon.oss
2022-02-04  8:41 ` [PATCH v3 3/5] gdb/arm: Introduce arm_cache_init christophe.lyon.oss
2022-02-04  8:41 ` [PATCH v3 4/5] gdb/arm: Add support for multiple stack pointers on Cortex-M christophe.lyon.oss
2022-02-04  8:41 ` [PATCH v3 5/5] gdb/arm: Extend arm_m_addr_is_magic to support FNC_RETURN, add unwind-ns-to-s command christophe.lyon.oss
2022-02-25  9:54 ` [PATCH v3 0/5] arm: Add support for multiple stacks on Cortex-M Maxim Kuvyrkov
2022-02-27 11:35   ` Joel Brobecker
2022-02-28 10:38     ` Christophe Lyon
2022-03-06 10:48       ` Joel Brobecker [this message]
2022-03-06 21:19         ` Christophe Lyon
2022-03-11  9:40           ` Yvan Roux
2022-03-11  9:47             ` Christophe Lyon

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=YiSRbD7kpzC+SrZr@adacore.com \
    --to=brobecker@adacore.com \
    --cc=Luis.Machado@arm.com \
    --cc=christophe.lyon@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=torbjorn.svensson@st.com \
    --cc=yvan.roux@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 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).