All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Nikita Shubin <nikita.shubin@maquefel.me>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hartley Sweeten <hsweeten@visionengravers.com>
Subject: Re: [RFC PATCH 0/3] gpio: ep93xx: convert to multi irqchips
Date: Mon, 28 Dec 2020 21:41:47 +0100	[thread overview]
Message-ID: <CACRpkdagGSLm8TVVj0Ox8EE+iqS=knS2AgKz2sycMWtOtBN4Nw@mail.gmail.com> (raw)
In-Reply-To: <115071609167990@mail.yandex.ru>

On Mon, Dec 28, 2020 at 4:14 PM <nikita.shubin@maquefel.me> wrote:

> I had such a thought, but I was stopped by the delusion that no one is using this
> hardware anymore.

It is definately *used* a lot. It is dubious if it is used with the
latest kernel.
Hartley was/is using it on engraving machinery and using the latest
kernel, I think his setup is pretty large.

The number of deployed machines using EP93xx is likely large, but
more importantly, as with MOXA Art it is likely to be internet connected
and managing vital control systems.

In short: nobody may be upgrading these kernels, but the definately
*should* be upgrading them. For security reasons.

So as a community hat I have concluded it would be socially unacceptable
to delete it and not offer an upgrade path for these systems the
day they realize "oh s.... that is an internet connected pressure boiler".

So if possible it should be modernized.

> Not promising anything right now - but such a job sounds like a real fun.

I would be grateful.

Yours,
Linus Walleij

      reply	other threads:[~2020-12-28 23:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24 11:22 [RFC PATCH 0/3] gpio: ep93xx: convert to multi irqchips Nikita Shubin
2020-12-24 11:22 ` [RFC PATCH 1/3] " Nikita Shubin
2020-12-26 17:52   ` Andy Shevchenko
2020-12-28 15:05     ` nikita.shubin
2020-12-24 11:22 ` [RFC PATCH 2/3] gpio: ep93xx: drop to_irq binding Nikita Shubin
2020-12-27 21:21   ` Linus Walleij
2021-01-04 14:17     ` Bartosz Golaszewski
2020-12-24 11:22 ` [RFC PATCH 3/3] gpio: ep93xx: specify gpio_irq_chip->first Nikita Shubin
2020-12-27 21:22   ` Linus Walleij
2020-12-26 17:34 ` [RFC PATCH 0/3] gpio: ep93xx: convert to multi irqchips Andy Shevchenko
2020-12-27 14:00   ` Linus Walleij
2020-12-27 13:55 ` Linus Walleij
2020-12-28 15:14   ` nikita.shubin
2020-12-28 20:41     ` Linus Walleij [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='CACRpkdagGSLm8TVVj0Ox8EE+iqS=knS2AgKz2sycMWtOtBN4Nw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita.shubin@maquefel.me \
    /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.