On 12/08/2017 09:24 PM, Josef Bacik wrote: > On Fri, Dec 08, 2017 at 04:35:44PM +0100, Daniel Borkmann wrote: >> On 12/06/2017 05:12 PM, Josef Bacik wrote: >>> Jon noticed that I had a typo in my _ASM_KPROBE_ERROR_INJECT macro. I went >>> to >>> figure out why the compiler didn't catch it and it's because it was not used >>> anywhere. I had copied it from the trace blacklist code without >>> understanding >>> where it was used as cscope didn't find the original macro I was looking >>> for, so >>> I assumed it was some voodoo and left it in place. Turns out cscope failed >>> me >>> and I didn't need the macro at all, the trace blacklist thing I was looking >>> at >>> was for marking assembly functions as blacklisted and I have no intention of >>> marking assembly functions as error injectable at the moment. >>> >>> v7->v8: >>> - removed the _ASM_KPROBE_ERROR_INJECT since it was not needed. >> >> The series doesn't apply cleanly to the bpf-next tree, so one last respin >> with >> a rebase would unfortunately still be required, thanks! > > I've rebased and let it sit in my git tree to make sure kbuild test bot didn't > blow up, can you pull from > > git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git > bpf-override-return > > or do you want me to repost the whole series? Thanks,
Yeah, the patches would need to end up on netdev, so once kbuild bot went through fine after your rebase, please send the series. Thanks, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
