linux-kernel - Re: [RESEND PATCH 1/2] iio:core: Introduce unlocked version of iio_map_array

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] [day] [month] [year] [list]

Message-ID: <20201129130821.2cb07ce4@archlinux>
Date:   Sun, 29 Nov 2020 13:08:21 +0000
From:   Jonathan Cameron <jic23@...nel.org>
To:     Lino Sanfilippo <LinoSanfilippo@....de>
Cc:     andy.shevchenko@...il.com, lars@...afoo.de, pmeerw@...erw.net,
        linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH 1/2] iio:core: Introduce unlocked version of
 iio_map_array_unregister()

On Sat, 28 Nov 2020 15:22:16 +0100
Lino Sanfilippo <LinoSanfilippo@....de> wrote:

> Hi Jonathan,
> 
> On 28.11.20 at 14:54, Jonathan Cameron wrote:
> 
> > A few notes to make it harder for people to do that in future.
> > 1. Don't send patch series (or new versions of older patches) in reply
> >    to an existing thread.   They get lost and difficult to pull out.
> >    b4 can't automatically figure out which patches to pull from that
> >    original thread for example.
> > 2. Always version number whole series with same number, even if some patches
> >    are new.   So this should be v3.
> >  
> 
> Thanks for these hints, I will keep it in mind for future patch submissions.

Mailing list seems to have recovered so I can use b4 again :)

Applied to the togreg branch of iio.git and pushed out as testing so the
autobuilders can try to find anything we missed.

Thanks,

Jonathan

> 
> Regards,
> Lino
>