From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755416AbcH1KZ7 (ORCPT ); Sun, 28 Aug 2016 06:25:59 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:16299 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755268AbcH1KZ6 (ORCPT ); Sun, 28 Aug 2016 06:25:58 -0400 X-IronPort-AV: E=Sophos;i="5.28,590,1464645600"; d="scan'208";a="191292506" Date: Sun, 28 Aug 2016 12:25:53 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: SF Markus Elfring cc: Julia Lawall , linux-cris-kernel@axis.com, Adam Buchbinder , Dave Hansen , Ingo Molnar , Jesper Nilsson , Jiri Kosina , Mikael Starvik , Thomas Gleixner , LKML , kernel-janitors@vger.kernel.org, Paolo Bonzini Subject: Re: [PATCH 8/8] cris-cryptocop: Apply another recommendation from "checkpatch.pl" In-Reply-To: <130cda68-feed-8b48-e928-7e915888c7c9@users.sourceforge.net> Message-ID: References: <566ABCD9.1060404@users.sourceforge.net> <0e29d372-ef5f-afa7-50b1-70ddc089ef00@users.sourceforge.net> <130cda68-feed-8b48-e928-7e915888c7c9@users.sourceforge.net> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 28 Aug 2016, SF Markus Elfring wrote: > >> @@ -2276,7 +2277,10 @@ static int cryptocop_job_setup(struct cryptocop_prio_job **pj, struct cryptocop_ > >> (*pj)->iop->ctx_in.saved_data = operation->list_op.inlist; > >> (*pj)->iop->ctx_in.saved_data_buf = operation->list_op.in_data_buf; > >> } else { > >> - if ((err = cryptocop_setup_dma_list(operation, &(*pj)->iop, alloc_flag))) { > >> + err = cryptocop_setup_dma_list(operation, > >> + &(*pj)->iop, > >> + alloc_flag); > > > > Checkpatch didn't say to put every argument on a different line, > > I agree to this information. > > > > and that wasn't done before, so why do it now? > > I tend to give each function parameter its own text line in such an use case > (for the known length limitation). > > > > There is plenty of room for at least &(*pj)->iop on the line before. > > This is true. - Do you prefer an other indentation approach here? Very much. Most of the kernel code puts as much information on a line as possible, unless there is a reason to do otherwise. Then more of the code will fit on the screen at one time. julia