All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
	jason.wessel@windriver.com, linux-arm-kernel@lists.infradead.org,
	kgdb-bugreport@lists.sourceforge.net, stable@vger.kernel.org
Subject: Re: [PATCH v2 0/3] arm64: kgdb: fix single stepping
Date: Fri, 23 Sep 2016 10:16:18 +0200	[thread overview]
Message-ID: <20160923081618.GH18056@kroah.com> (raw)
In-Reply-To: <20160923073327.9657-1-takahiro.akashi@linaro.org>

On Fri, Sep 23, 2016 at 04:33:24PM +0900, AKASHI Takahiro wrote:
> Kgdb support on arm64 was merged in v3.15, but from its first appearance,
> "signle step" has never worked well.
> 
> This patch fixes all the error cases I found so far.
> The original patch[1] was splitted into three pieces, ones for each case.
> patch#1, #2 should be applied to all the version, v3.15 and later.
> pathc#3 only for v3.16 and later.

As this is not a regression (i.e. it has never worked), why is this
something for stable releases?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] arm64: kgdb: fix single stepping
Date: Fri, 23 Sep 2016 10:16:18 +0200	[thread overview]
Message-ID: <20160923081618.GH18056@kroah.com> (raw)
In-Reply-To: <20160923073327.9657-1-takahiro.akashi@linaro.org>

On Fri, Sep 23, 2016 at 04:33:24PM +0900, AKASHI Takahiro wrote:
> Kgdb support on arm64 was merged in v3.15, but from its first appearance,
> "signle step" has never worked well.
> 
> This patch fixes all the error cases I found so far.
> The original patch[1] was splitted into three pieces, ones for each case.
> patch#1, #2 should be applied to all the version, v3.15 and later.
> pathc#3 only for v3.16 and later.

As this is not a regression (i.e. it has never worked), why is this
something for stable releases?

thanks,

greg k-h

  parent reply	other threads:[~2016-09-23  8:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23  7:33 [PATCH v2 0/3] arm64: kgdb: fix single stepping AKASHI Takahiro
2016-09-23  7:33 ` AKASHI Takahiro
2016-09-23  7:33 ` [PATCH v2 1/3] " AKASHI Takahiro
2016-09-23  7:33   ` AKASHI Takahiro
2016-09-23  7:33 ` [PATCH v2 2/3] arm64: kgdb: prevent kgdb from being invoked recursively AKASHI Takahiro
2016-09-23  7:33   ` AKASHI Takahiro
2016-09-23 10:02   ` Will Deacon
2016-09-23 10:02     ` Will Deacon
2016-09-23  7:33 ` [PATCH v2 3/3] arm64: kgdb: disable interrupts while a software step is enabled AKASHI Takahiro
2016-09-23  7:33   ` AKASHI Takahiro
2016-09-23  8:16 ` Greg KH [this message]
2016-09-23  8:16   ` [PATCH v2 0/3] arm64: kgdb: fix single stepping Greg KH
2016-09-23  8:32   ` AKASHI Takahiro
2016-09-23  8:32     ` AKASHI Takahiro
2016-09-23  8:43     ` Greg KH
2016-09-23  8:43       ` Greg KH
2016-09-23  9:27       ` AKASHI Takahiro
2016-09-23  9:27         ` AKASHI Takahiro
2016-09-23  9:23         ` Greg KH
2016-09-23  9:23           ` Greg KH

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=20160923081618.GH18056@kroah.com \
    --to=greg@kroah.com \
    --cc=catalin.marinas@arm.com \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=will.deacon@arm.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 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.