linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Federico Vaga <federico.vaga@cern.ch>,
	Pat Riehecky <riehecky@fnal.gov>,
	Alessandro Rubini <rubini@gnudd.com>
Subject: Re: [PATCH] fmc: Delete the FMC subsystem
Date: Wed, 12 Jun 2019 14:27:12 +0200	[thread overview]
Message-ID: <CACRpkdYrL110Ae-FkVJ83=MStDbeZy63aJQotZg3MdG5+gxrAA@mail.gmail.com> (raw)
In-Reply-To: <20190610141809.17542-1-linus.walleij@linaro.org>

On Mon, Jun 10, 2019 at 4:18 PM Linus Walleij <linus.walleij@linaro.org> wrote:

> The FMC subsystem was created in 2012 with the ambition to
> drive development of drivers for this hardware upstream.
>
> The current implementation has architectural flaws and would
> need to be revamped using real hardware to something that can
> reuse existing kernel abstractions in the subsystems for e.g.
> I2C, FPGA and GPIO.
>
> We have concluded that for the mainline kernel it will be
> better to delete the subsystem and start over with a clean
> slate when/if an active maintainer steps up.
>
> For details see:
> https://lkml.org/lkml/2018/10/29/534
>
> Suggested-by: Federico Vaga <federico.vaga@cern.ch>
> Cc: Federico Vaga <federico.vaga@cern.ch>
> Cc: Pat Riehecky <riehecky@fnal.gov>
> Cc: Alessandro Rubini <rubini@gnudd.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

After consent from the authors I have queued the removal in
the GPIO subsystem tree.

Yours,
Linus Walleij

      parent reply	other threads:[~2019-06-12 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 14:18 [PATCH] fmc: Delete the FMC subsystem Linus Walleij
2019-06-11  8:05 ` Alessandro Rubini
2019-06-11 16:40 ` Federico Vaga
2019-06-12 12:27 ` 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='CACRpkdYrL110Ae-FkVJ83=MStDbeZy63aJQotZg3MdG5+gxrAA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=federico.vaga@cern.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riehecky@fnal.gov \
    --cc=rubini@gnudd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).