Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1290749 > unrolled thread
| Started by | Jeff Merkey <linux.mdb@gmail.com> |
|---|---|
| First post | 2015-12-14 00:20 +0100 |
| Last post | 2015-12-14 00:20 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | Jeff Merkey <linux.mdb@gmail.com> |
|---|---|
| Date | 2015-12-14 00:20 +0100 |
| Subject | Re: [PATCH v2 1/1] Fix int1 recursion when no perf_bp_event is registeredy |
| Message-ID | <qFo5Q-6pM-31@gated-at.bofh.it> |
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 top | Article view | linux.kernel
csiph-web