All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Cc: andy.shevchenko@gmail.com, lars@metafoo.de, pmeerw@pmeerw.net,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 1/2] iio:core: Introduce unlocked version of iio_map_array_unregister()
Date: Sun, 29 Nov 2020 13:08:21 +0000	[thread overview]
Message-ID: <20201129130821.2cb07ce4@archlinux> (raw)
In-Reply-To: <b933efbe-133e-bece-5516-2ecf3dc120b0@gmx.de>

On Sat, 28 Nov 2020 15:22:16 +0100
Lino Sanfilippo <LinoSanfilippo@gmx.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
> 


      reply	other threads:[~2020-11-29 13:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 13:44 [RESEND PATCH 1/2] iio:core: Introduce unlocked version of iio_map_array_unregister() Lino Sanfilippo
2020-11-28 13:44 ` [RESEND PATCH 2/2] io:core: In iio_map_array_register() cleanup in case of error Lino Sanfilippo
2020-11-28 13:54 ` [RESEND PATCH 1/2] iio:core: Introduce unlocked version of iio_map_array_unregister() Jonathan Cameron
2020-11-28 14:22   ` Lino Sanfilippo
2020-11-29 13:08     ` Jonathan Cameron [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201129130821.2cb07ce4@archlinux \
    --to=jic23@kernel.org \
    --cc=LinoSanfilippo@gmx.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.