Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751901Ab3FAP0x (ORCPT ); Sat, 1 Jun 2013 11:26:53 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:35056 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750830Ab3FAP0p (ORCPT ); Sat, 1 Jun 2013 11:26:45 -0400 Message-ID: <1370100403.2463.14.camel@dabdike> Subject: Re: [PATCH] [SCSI] libsas: Cocci spatch "ptr_ret.spatch" From: James Bottomley To: Thomas Meyer Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Date: Sat, 01 Jun 2013 08:26:43 -0700 In-Reply-To: <1370080781.29224.39.camel@localhost.localdomain> References: <1370080781.29224.39.camel@localhost.localdomain> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.8.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1152 Lines: 32 On Sat, 2013-06-01 at 11:59 +0200, Thomas Meyer wrote: > Signed-off-by: Thomas Meyer > --- > > diff -u -p a/drivers/scsi/libsas/sas_scsi_host.c b/drivers/scsi/libsas/sas_scsi_host.c > --- a/drivers/scsi/libsas/sas_scsi_host.c > +++ b/drivers/scsi/libsas/sas_scsi_host.c > @@ -1093,9 +1093,7 @@ int sas_init_queue(struct sas_ha_struct > > core->queue_thread = kthread_run(sas_queue_thread, sas_ha, > "sas_queue_%d", core->shost->host_no); > - if (IS_ERR(core->queue_thread)) > - return PTR_ERR(core->queue_thread); > - return 0; > + return PTR_RET(core->queue_thread); > } Really, no, this is not a good patch. I know exactly what the current code is doing by reading it. With your patch I now have to go and look up the definition of an obscure and non-standard macro. If we're sacrificing clarity, I want a good reason and having two lines fewer code isn't it. James -- 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/