linux-kernel - Re: [PATCH v3 3/5] iio: pressure: bmp280: simplify driver initialization logic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <046a29a5191c53813ce9477000b07c21ca5699fc.camel@gmail.com>
Date:   Mon, 11 Jul 2022 14:45:06 +0200
From:   Angel Iglesias <ang.iglesiasg@...il.com>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Jonathan Cameron <jic23@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Paul Cercueil <paul@...pouillou.net>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/5] iio: pressure: bmp280: simplify driver
 initialization logic

On dom, 2022-07-10 at 21:41 +0300, Andy Shevchenko wrote:
> It seems you somehow managed to send patches separately from email
> perspective.
> Make sure you pass parameter --thread to `git format-patch`, so it will create
> a proper chain of emails.

How should I proceed to fix this issue? Should I wait for more feedback and send
a new revision of the patches, now as a proper mail chain? Or should I resend
current patchset as a chain? I don't want to spam the mailing list more due to
my inexperience contributing.

> On Sun, Jul 10, 2022 at 11:17:06AM +0200, Angel Iglesias wrote:
> > Simplified common initialization logic of different sensor types
> > unifying calibration and initial configuration recovery.
> > 
> > Default config param values of each sensor type are stored inside
> > chip_info structure and used to initialize sensor data struct instance.
> > 
> > The auxiliar functions for read each sensor type calibration are converted
> > to a callback available on the chip_info struct.
> 
> > Signed-off-by: Angel Iglesias <ang.iglesiasg@...il.com>
> > Suggested-by: Jonathan Cameron <jic23@...nel.org>
> 
> Usually this kind of tag goes before your SoB, because it's chronologically
> correct.
> 
Ok, makes sense.

Thank you for your time and help,

Best regards,
Angel