Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C5A2CC74A5B for ; Fri, 17 Mar 2023 07:14:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230261AbjCQHOY (ORCPT ); Fri, 17 Mar 2023 03:14:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39304 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230290AbjCQHOU (ORCPT ); Fri, 17 Mar 2023 03:14:20 -0400 Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 73C7F60A8E for ; Fri, 17 Mar 2023 00:14:02 -0700 (PDT) Received: by mail-pj1-x1033.google.com with SMTP id fy10-20020a17090b020a00b0023b4bcf0727so4283548pjb.0 for ; Fri, 17 Mar 2023 00:14:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679037241; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=vRnYDcnKGtoBZkuiq/lt8z18fHea+PPaGqCtFysWiDM=; b=Nu7S65ypJG2PIfGNW0iHhiUGstx6Bvqkj4/u3/WGGd+wT60t6X66xPg1wP3DZfo9pW 0h5NptbuVJITIdJHK81E9YPL7ZAmmYhrmdsdAs32GwDtfRNqwt13CTTDGfNfbNuj3SPo R/TrpXgmbu50h6jZGAKOFDwefacpNgCbEl1LvP2MKcm5iGpFxWQuxvt3k8DZJ3AHXA8h bFmVZMWlaxrqI/0XbNAlj5Dz/6XixjSqu8VVw9Aq4aYpgwbkCO0h7usP8DcPulRIjPXL 3w/pu4McmQ8dZdbZMk6yAw6D/NOlxvsYUI30nvA5wf6mhALvau3IosRdyHtWHgz5vf/s EdqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679037241; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=vRnYDcnKGtoBZkuiq/lt8z18fHea+PPaGqCtFysWiDM=; b=kN0dYEDWa5IBMCoybuX8iWR12VdVqKPIdFxeJpeASDKcDYtj25ETqz8kCoje/9UF9r X+3lUigW6aqC/p1yeztUMDcX5MWl9MDazOSpIWU1d9fzs+aDHpJHruldJQJalWJhUYBm 9Y1MRVH1DSWEeu58YWUbim34Q+nsVC4rsrhF40ZsBTBH2EjiW8Jwyx7nEohmsOUB5xlK iaIifYNzIf9pbksE6nvNoCgE/iizUJsMeMQTKINac6ppsV4u0RhKNdUsKLNFL7xA4bQm Nc7KLUqeQ+yiuDa1e3EN/qumKpR8zZIFjBFvjXV2dDaikP96WSvqI95jOt90grZ+KXQt /RlA== X-Gm-Message-State: AO0yUKW+F9KNqskLfxPFM69mObS6+scPw3WXCsspbRtd79AYMuwusvA+ ovLtdyJrozBJgIDAAciKDv8= X-Google-Smtp-Source: AK7set/bVwRCYhq47jmjk2ofdd77sALIsCyt/iRjdk71zK5ugzcRKSKf5IKBF9BprY4TafrIYOiQ2g== X-Received: by 2002:a05:6a20:7351:b0:b8:a0e1:2739 with SMTP id v17-20020a056a20735100b000b8a0e12739mr7859667pzc.3.1679037241480; Fri, 17 Mar 2023 00:14:01 -0700 (PDT) Received: from sumitra.com ([14.139.226.12]) by smtp.gmail.com with ESMTPSA id p18-20020a62ab12000000b005a8f1d76d46sm864281pff.13.2023.03.17.00.13.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Mar 2023 00:14:00 -0700 (PDT) Date: Fri, 17 Mar 2023 00:13:52 -0700 From: Sumitra Sharma To: Julia Lawall Cc: drv@mailo.com, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev, outreachy@lists.linux.dev Subject: Re: [PATCH v4] Staging: octeon: Fix line ending with '(' Message-ID: <20230317071352.GA83845@sumitra.com> References: <20230317052455.GA83442@sumitra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 17, 2023 at 07:03:08AM +0100, Julia Lawall wrote: > > > On Thu, 16 Mar 2023, Sumitra Sharma wrote: > > > Since the coding style limited the code to 80 columns per line which caused > > splitting the function header into two lines resulted in the first line > > ending with a '('. This caused the checkpatch error. > > The first sentence is still not really grammatical. Something like: > > The coding style used to limit lines to 80 characters, which led to > splitting this function header into multiple lines, and ending thie first > line with a (. > > For checkpatch, is it an error or a warning? > HI julia, Yes, you are correct, I did the mistake its not the error but a check. How about this... ### The coding style used to limit lines to 80 characters, which led to splitting this function header into multiple lines and ending the first line with a '('. This split causes a check reported by the checkpatch. Place the function parameters immediately after '(' in a single line to align the function header. ### Thank you for your reviews. Regards, Sumitra > julia > > > > > Place the function parameters immediately after '(' in a single > > line to align the function header. > > > > Signed-off-by: Sumitra Sharma > > --- > > v2: Change patch subject and description > > > > v3: Change patch description, noted by Deepak R Varma > > > > > > v4: Correct grammartical mistakes, noted by Julia Lawall > > > > > > > > > > drivers/staging/octeon/octeon-stubs.h | 4 +--- > > 1 file changed, 1 insertion(+), 3 deletions(-) > > > > diff --git a/drivers/staging/octeon/octeon-stubs.h b/drivers/staging/octeon/octeon-stubs.h > > index 7a02e59e283f..3e7b92cd2e35 100644 > > --- a/drivers/staging/octeon/octeon-stubs.h > > +++ b/drivers/staging/octeon/octeon-stubs.h > > @@ -1372,9 +1372,7 @@ static inline void cvmx_fau_async_fetch_and_add32(uint64_t scraddr, > > int32_t value) > > { } > > > > -static inline union cvmx_gmxx_rxx_rx_inbnd cvmx_spi4000_check_speed( > > - int interface, > > - int port) > > +static inline union cvmx_gmxx_rxx_rx_inbnd cvmx_spi4000_check_speed(int interface, int port) > > { > > union cvmx_gmxx_rxx_rx_inbnd r; > > > > -- > > 2.25.1 > > > > > >