[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VfYVVPuNmukq9Civ2vHu_au5Nj-MPm5JXDHiTaMXpyzUQ@mail.gmail.com>
Date: Mon, 11 Jul 2022 15:11:23 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Angel Iglesias <ang.iglesiasg@...il.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
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 <linux-iio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 3/5] iio: pressure: bmp280: simplify driver
initialization logic
On Mon, Jul 11, 2022 at 2:46 PM Angel Iglesias <ang.iglesiasg@...il.com> wrote:
> 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.
Since there are already comments and more might come, wait a few days
and send a new version.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists