From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] arm64: kgdb: fix single stepping
Date: Fri, 16 Sep 2016 08:45:13 +0100 [thread overview]
Message-ID: <20160916074513.GI3380@arm.com> (raw)
In-Reply-To: <20160916043218.GA30248@linaro.org>
A Jason appeared!
On Fri, Sep 16, 2016 at 01:32:19PM +0900, AKASHI Takahiro wrote:
> On Thu, Sep 15, 2016 at 08:04:57AM -0500, Jason Wessel wrote:
> > I added the patch to kgdb-next after fixing up the context since it no
> > longer applied to the mainline (
> > https://git.kernel.org/cgit/linux/kernel/git/jwessel/kgdb.git/log/?h=kgdb-next).
> > If there is further discussion on the point above, another patch can be
> > added, but it I am assuming this is the way you desire it to work as
> > there are some other architectures that use the same behaviour. I do
> > not presently have any ARM64 hardware to validate this particular
> > change.
> >
> > I also added to the patch a "Cc: linux-stable <stable@vger.kernel.org>"
> > so we can have this appear on some of the older kernels.
>
> Since Will asked me to split this patch into a few, I need some reworks
> to clarify which hunks in the patch are necessary for which version of kernel.
Yes, splitting the patch would be much better for sorting out the stable
backports too. Jason, please can you drop the patch for now? I don't mind
whether the end result goes via arm64 or kgdb, but we should at least both
agree on it first :)
Will
next prev parent reply other threads:[~2016-09-16 7:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 1:13 [RESEND PATCH] arm64: kgdb: fix single stepping AKASHI Takahiro
2016-09-14 12:48 ` Giuseppe CAVALLARO
2016-09-14 14:58 ` Will Deacon
2016-09-15 7:56 ` AKASHI Takahiro
2016-09-15 10:41 ` Daniel Thompson
2016-09-15 12:32 ` Jason Wessel
2016-09-15 13:04 ` Jason Wessel
2016-09-16 4:32 ` AKASHI Takahiro
2016-09-16 7:45 ` Will Deacon [this message]
2016-09-19 22:25 ` Jason Wessel
2016-09-19 22:29 ` Jason Wessel
2016-09-20 8:43 ` AKASHI Takahiro
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=20160916074513.GI3380@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).