From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Ferry Toth <ftoth@exalondelft.nl>
Subject: Re: [PATCH v1 1/1] Revert "pinctrl: avoid unsafe code pattern in find_pinctrl()"
Date: Thu, 19 Oct 2023 15:15:09 +0300 [thread overview]
Message-ID: <ZTEdzVViUPdk3pk/@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdZ0cnJpYuzU=47-oW-7N_YGMo2vXpKOeXeNi5PhPY7QMA@mail.gmail.com>
On Thu, Oct 19, 2023 at 10:12:57AM +0200, Linus Walleij wrote:
> On Thu, Oct 19, 2023 at 12:41 AM Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
...
> > Given that there are more issues in that code, maybe we should revert
> > the patch for now so Andy has a chance to convert to UUID/LABEL booting?
>
> Yeah I reverted it, the above elaboration may apply to this patch
> too and makes me feel we are "mostly safe" in this regard anyway.
Thank you!
And on my side I'll try my best to avoid static enumerations.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-10-19 12:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 14:18 [PATCH v1 1/1] Revert "pinctrl: avoid unsafe code pattern in find_pinctrl()" Andy Shevchenko
2023-10-17 18:18 ` Linus Walleij
2023-10-17 18:34 ` Andy Shevchenko
2023-10-17 18:39 ` Andy Shevchenko
2023-10-17 18:59 ` Linus Walleij
2023-10-17 19:45 ` Andy Shevchenko
2023-10-17 21:43 ` Dmitry Torokhov
2023-10-18 5:01 ` Andy Shevchenko
2023-10-18 22:41 ` Dmitry Torokhov
2023-10-19 8:12 ` Linus Walleij
2023-10-19 12:15 ` Andy Shevchenko [this message]
2023-10-19 12:13 ` Andy Shevchenko
2023-10-19 16:52 ` Andy Shevchenko
2023-10-19 17:19 ` Andy Shevchenko
2023-10-18 7:56 ` Ferry Toth
2023-10-19 8:13 ` Linus Walleij
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=ZTEdzVViUPdk3pk/@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ftoth@exalondelft.nl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulf.hansson@linaro.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 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.