On Tue, 10 Nov 2015, Greg Kroah-Hartman wrote: > On Tue, Nov 10, 2015 at 06:31:47PM -0500, Mikulas Patocka wrote: > > > > > > On Tue, 10 Nov 2015, Greg Kroah-Hartman wrote: > > > > > On Tue, Nov 10, 2015 at 01:32:10PM -0500, Mikulas Patocka wrote: > > > > Fix the warning drivers/target/target_core_pr.c:332:3: warning: 'return' > > > > with no value, in function returning non-void [-Wreturn-type] > > > > > > > > The patch 35afa65642a9a88c81913377b93a3a66220f8b9d committed to 4.1.11 > > > > adds a check if device_list is NULL. The patch adds a return statement > > > > without a value to the function core_scsi3_pr_seq_non_holder that returns > > > > int. > > > > > > > > Signed-off-by: Mikulas Patocka <mpatocka@xxxxxxxxxx> > > > > > > > > --- > > > > drivers/target/target_core_pr.c | 2 +- > > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > <formletter> > > > > > > This is not the correct way to submit patches for inclusion in the > > > stable kernel tree. Please read Documentation/stable_kernel_rules.txt > > > for how to do this properly. > > > > > > </formletter> > > > > This patch has no upstream equivalent (because the code in upstream was > > already refactored), so none of the rules in stable_kernel_rules.txt apply > > to it. The patch that broke it also has no upstream equivalent. > > > > Then you need to say that! > > And the fact that a "please take this patch, it's correct but doesn't > apply to upstream" patch is now broken is proof of why I didn't want to > take it in the first place! > > Ugh. How about I just revert the original patch and then you send me > backports of what is actually in Linus's tree so we don't have this > problem anymore? The original patch that caused this compilation warning fixes some crashes, so you should not revert it. You can work with subsystem maintainers on backporting the refactored code from upstream to 4.1 - I don't know how hard or possible it is. Mikulas > Oh, and you got the stable mailing list address wrong as well :( > > Please fix all of this up and resend. > > thanks, > > greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html