From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexander Aring <alex.aring@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v1 1/1] ieee802154: ca8210: Remove stray gpiod_unexport() call
Date: Thu, 1 Jun 2023 19:32:29 +0300 [thread overview]
Message-ID: <ZHjIHZv4o8JaX7Dt@smile.fi.intel.com> (raw)
In-Reply-To: <20230529101213.46f4f2b1@xps-13>
On Mon, May 29, 2023 at 10:12:13AM +0200, Miquel Raynal wrote:
> andriy.shevchenko@linux.intel.com wrote on Sun, 28 May 2023 17:09:38
> +0300:
>
> > There is no gpiod_export() and gpiod_unexport() looks pretty much stray.
> > The gpiod_export() and gpiod_unexport() shouldn't be used in the code,
> > GPIO sysfs is deprecated. That said, simply drop the stray call.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Any reason not to consider a backport into stable kernels?
> Cc: stable + Fixes would certainly be welcome in this case?
I don't think it's justified for stable. It doesn't fix any existing regression
as far as I understand.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-01 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 14:09 [PATCH net-next v1 1/1] ieee802154: ca8210: Remove stray gpiod_unexport() call Andy Shevchenko
2023-05-29 8:12 ` Miquel Raynal
2023-06-01 16:32 ` Andy Shevchenko [this message]
2023-05-30 7:42 ` Simon Horman
2023-06-05 14:09 ` Andy Shevchenko
2023-06-06 9:33 ` Alexander Aring
2023-06-06 9:47 ` Miquel Raynal
2023-06-06 9:50 ` Alexander Aring
2023-06-06 13:03 ` Andy Shevchenko
2023-06-06 18:52 ` Miquel Raynal
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=ZHjIHZv4o8JaX7Dt@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox