Re: [PATCH v2 1/1] Fix int1 recursion when no perf_bp_event is registeredy

From	Jeff Merkey <linux.mdb@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v2 1/1] Fix int1 recursion when no perf_bp_event is registeredy
Date	2015-12-14 00:20 +0100
Message-ID	<qFo5Q-6pM-31@gated-at.bofh.it> (permalink)
References	<qE3G9-2Ub-5@gated-at.bofh.it> <qEeBz-1xO-5@gated-at.bofh.it> <qEeLg-1Qp-3@gated-at.bofh.it> <qEgtI-2KO-23@gated-at.bofh.it> <qEqW6-1rK-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Is there anything else I need to do on this patch, is it acceptable,
do you want a v3 that disables the errant breakpoints?  Problem with
that approach is if in fact there is a "lazy" breakpoint we might end
up clearing it being set if it fires off too soon.

So this is the first time I have submitted a patch through this new
process so what happens now?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH v2 1/1] Fix int1 recursion when no perf_bp_event is registeredy Jeff Merkey <linux.mdb@gmail.com> - 2015-12-14 00:20 +0100

csiph-web