From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8B0F2C433E1 for ; Tue, 19 May 2020 10:19:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 69E1F207D8 for ; Tue, 19 May 2020 10:19:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="j92WI0OI" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728224AbgESKT6 (ORCPT ); Tue, 19 May 2020 06:19:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45934 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725911AbgESKTz (ORCPT ); Tue, 19 May 2020 06:19:55 -0400 Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C3747C061A0C; Tue, 19 May 2020 03:19:54 -0700 (PDT) Received: by mail-wr1-x441.google.com with SMTP id y3so15284608wrt.1; Tue, 19 May 2020 03:19:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=pnjDftxxSSPg8a99O3CMzTvnM8zCPLUpID8zm/35UjQ=; b=j92WI0OIbflFRPQPu3EVYEQCvUEHlpg8TNKie8Beddr2IZAmB12I4LVEPNspm91VhN JGjXQtCh/T9GV70oOyMtjSPW0EupYoofuknbthtxs3AQ+wyZAInAArOUkaLuS/XfEdVs cK3coxk8E4uQjdJgipJRssjbq9EiOsN/sYI98xSiOefKyCmr0J/u387xBUphmoHMbkkl VUi/SfYUYd/uRah0Zu9WgsbFLNd+e8tEdu4siwlc+cTMCd5eQ4R3IwkiCSEm+aC6ygB4 t2z6egwiRYZ5V5uGKfpyZLY+kratcqS/UBWtS0MdLEKm/UAFvNVZZILxdZK5tDE+9ijZ FMpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=pnjDftxxSSPg8a99O3CMzTvnM8zCPLUpID8zm/35UjQ=; b=n+jTHeuBQVIfclbKSmlpZS0Mmmm1lPvYsoEnjVsLCXDgETq+EPj3OqvgfX5Sgg1Khg f0onkM9cTtF6drc0xwOFHONBBAsdE3wWCYATPe4R7PO/GWon8668odYZRKEGszLcCZaj dF6F/sV68so8Wt9arh6cNCZxEBzo1ohaCsa5W+clTyRzajCIByByU0gQj6iCht9jINl4 N4kZpv8Fx1HJIDLl1nAy0+1v3FJ+UDLP0jRhskBqh1ThmWfgeLXV7Yt1WojXOUuCUX0l HqfQ0/lVc7BCcKJDkeJzY06Si+I8/ocLIGukhdwiZrhyR8bVqRMwmVtJNzdmMJzIRN9T hK6A== X-Gm-Message-State: AOAM530jFtIRWvYcjcdmudYTOp/Fia8oXhSr8XtfSCZ1Q0bUWajK67TI s8okAJ9VeyZ8K2q30wjJK1g= X-Google-Smtp-Source: ABdhPJwAAtM0HgwUVFHhrsukc4a3ep+2NwtT5kMvoesLWOhh1z3TGoe3Ra/t6CXKylk7qCMmjyUatg== X-Received: by 2002:adf:db52:: with SMTP id f18mr24759961wrj.258.1589883593425; Tue, 19 May 2020 03:19:53 -0700 (PDT) Received: from ict14-OptiPlex-980 ([178.23.248.46]) by smtp.gmail.com with ESMTPSA id g6sm20265410wrp.75.2020.05.19.03.19.51 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 May 2020 03:19:52 -0700 (PDT) Date: Tue, 19 May 2020 12:19:50 +0200 From: Jonathan Albrieux To: Andy Shevchenko Cc: linux-kernel@vger.kernel.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Greg Kroah-Hartman , Hartmut Knaack , Jonathan Cameron , Lars-Peter Clausen , Linus Walleij , "open list:IIO SUBSYSTEM AND DRIVERS" , Peter Meerwald-Stadler , Thomas Gleixner Subject: Re: [PATCH v2 0/3] iio: magnetometer: ak8975: Add gpio reset support Message-ID: <20200519101950.GC10391@ict14-OptiPlex-980> References: <20200519065749.4624-1-jonathan.albrieux@gmail.com> <20200519092212.GT1634618@smile.fi.intel.com> <20200519094835.GB10391@ict14-OptiPlex-980> <20200519100815.GA1634618@smile.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200519100815.GA1634618@smile.fi.intel.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 19, 2020 at 01:08:15PM +0300, Andy Shevchenko wrote: > On Tue, May 19, 2020 at 11:48:35AM +0200, Jonathan Albrieux wrote: > > On Tue, May 19, 2020 at 12:22:12PM +0300, Andy Shevchenko wrote: > > > On Tue, May 19, 2020 at 08:57:40AM +0200, Jonathan Albrieux wrote: > > ... > > > > I dunno if it's your first submission to Linux kernel project or other OSS, > > > but here you missed a changelog. Rule of thumb is to provide a summary of > > > the changes done in the history of the evolution of a patch series. > > > > > > > Oh thank you and sorry for not having included it. > > > > Does the changelog needs to be added to all patch files or just on the ones > > subject of the changes? > > Up to you and maintainer of the corresponding subsystem. > > My common sense tells me that > 1) if there is a cover letter, just put a joined changelog there > 2) otherwise, put changelog in each patch. > > I saw in practice all possible variants, i.e. > a) cover letter w/o changelog + changelog per patch; > b) cover letter w/ changelog + changelog per patch; > c) cover letter w/ changelog. > > I think any of it is fine in general. > > -- > With Best Regards, > Andy Shevchenko > > Thank you for the tips, will work on it! Best regards, Jonathan Albrieux