From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
christophe.leroy@c-s.fr, mikey@neuling.org
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
linux-kernel@vger.kernel.org, npiggin@gmail.com,
paulus@samba.org, naveen.n.rao@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v6 1/7] Powerpc/Watchpoint: Introduce macros for watchpoint length
Date: Thu, 14 Nov 2019 20:07:53 +1100 (AEDT) [thread overview]
Message-ID: <47DFxj5f70z9sRm@ozlabs.org> (raw)
In-Reply-To: <20191017093204.7511-2-ravi.bangoria@linux.ibm.com>
On Thu, 2019-10-17 at 09:31:58 UTC, Ravi Bangoria wrote:
> We are hadrcoding length everywhere in the watchpoint code.
> Introduce macros for the length and use them.
>
> Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b811be615cb78c90fca42bbd5b958427d03ba7e0
cheers
next prev parent reply other threads:[~2019-11-14 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:31 [PATCH v6 0/7] Powerpc/Watchpoint: Few important fixes Ravi Bangoria
2019-10-17 9:31 ` [PATCH v6 1/7] Powerpc/Watchpoint: Introduce macros for watchpoint length Ravi Bangoria
2019-11-14 9:07 ` Michael Ellerman [this message]
2019-10-17 9:31 ` [PATCH v6 2/7] Powerpc/Watchpoint: Fix length calculation for unaligned target Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 3/7] Powerpc/Watchpoint: Fix ptrace code that muck around with address/len Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 4/7] Powerpc/Watchpoint: Don't ignore extraneous exceptions blindly Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 5/7] Powerpc/Watchpoint: Rewrite ptrace-hwbreak.c selftest Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 6/7] Powerpc/Watchpoint: Add dar outside test in perf-hwbreak.c selftest Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 7/7] Powerpc/Watchpoint: Support for 8xx in ptrace-hwbreak.c selftest Ravi Bangoria
2019-10-29 4:54 ` [PATCH v6 0/7] Powerpc/Watchpoint: Few important fixes Ravi Bangoria
2019-10-29 14:01 ` Christophe Leroy
2019-11-07 14:30 ` Ravi Bangoria
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=47DFxj5f70z9sRm@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=ravi.bangoria@linux.ibm.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 NNTP newsgroup(s).