From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: "Antti Keränen" <detegr@rbx.email>
Cc: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>,
"Hannu Hartikainen" <hannu@hrtk.in>,
Lars-Peter Clausen <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
Nuno Sa <nuno.sa@analog.com>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: adis: set GPIO reset pin direction
Date: Wed, 14 Jul 2021 13:40:05 +0100 [thread overview]
Message-ID: <20210714134005.00001322@Huawei.com> (raw)
In-Reply-To: <20210714100445.hr73r2dfkxf36f35@haukka.localdomain>
On Wed, 14 Jul 2021 13:04:45 +0300
Antti Keränen <detegr@rbx.email> wrote:
> On Tue, Jul 13, 2021 at 06:53:11PM +0100, Jonathan Cameron wrote:
> > So this sits on the boundary of whether it is a fix or not.
> > Do we want this to go into rc1 + stable?
>
> I'm not familiar enough with kernel development to give any opinions of
> where this should go, but I would say this is a fix as the current code
> won't work with certain hardware configurations.
>
> > If so a fixes tag would be great.
>
> This would mean a v3 patch with fixes tag included into the commit
> message, right?
>
Send the fixes tag in reply to this and I'll make sure it's added.
No need to bother with a v3 for just that.
Thanks,
Jonathan
next prev parent reply other threads:[~2021-07-14 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 9:29 [RESEND PATCH] iio: adis: set GPIO reset pin direction Antti Keränen
2021-07-07 8:18 ` Lars-Peter Clausen
2021-07-07 8:36 ` Sa, Nuno
2021-07-07 11:53 ` Hannu Hartikainen
2021-07-07 12:25 ` Lars-Peter Clausen
2021-07-07 13:30 ` Hannu Hartikainen
2021-07-08 9:54 ` [PATCH v2] " Antti Keränen
2021-07-08 10:05 ` Sa, Nuno
2021-07-10 17:35 ` Jonathan Cameron
2021-07-13 17:53 ` Jonathan Cameron
2021-07-14 10:04 ` Antti Keränen
2021-07-14 12:40 ` Jonathan Cameron [this message]
2021-07-14 18:25 ` Antti Keränen
2021-07-17 17:41 ` Jonathan Cameron
2021-07-07 12:32 ` [RESEND PATCH] " Sa, Nuno
2021-07-07 12:32 ` Lars-Peter Clausen
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=20210714134005.00001322@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=detegr@rbx.email \
--cc=hannu@hrtk.in \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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.