On Fri, Jun 3, 2016 at 8:57 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > >> I guess I could take your patch as I only need it to build but have >> to remove -Werror option for that. My nightly testing does not invoke >> the devcoredump explicitly. It will when our 802.11 psm hangs. >> > > Well, then you don't really need to do anything - the only problem > would be with drivers that need the new method (none yet); the compiler > warning about the prototype mismatch is actually harmless (a function > that used to take a "const void *" now gets a "void *") That might be true, but I still get error below preparing the backports package: Failed to apply changes from backport-adjustments/devcoredump.patch > patching file compat/drivers-base-devcoredump.c > Hunk #1 succeeded at 31 (offset 1 line). > Hunk #2 succeeded at 41 with fuzz 1 (offset 1 line). > Hunk #3 succeeded at 74 (offset 1 line). > Hunk #4 succeeded at 86 (offset 1 line). > Hunk #5 succeeded at 122 (offset 1 line). > Hunk #6 succeeded at 134 (offset 1 line). > Hunk #7 succeeded at 179 (offset 1 line). > Hunk #8 succeeded at 325 (offset 44 lines). > Hunk #9 succeeded at 372 with fuzz 2 (offset 65 lines). > patching file include/linux/backport-devcoredump.h > Hunk #1 FAILED at 5. > Hunk #2 succeeded at 100 with fuzz 2 (offset 70 lines). > 1 out of 2 hunks FAILED -- saving rejects to file include/linux/backport-devcoredump.h.rej Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe backports" in
