public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Rob Springer <rspringer@google.com>,
	Todd Poynor <toddpoynor@google.com>,
	Ben Chan <benchan@chromium.org>, Richard Yeh <rcy@google.com>,
	linux-staging@lists.linux.dev, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gasket: remove it from the kernel
Date: Thu, 25 Mar 2021 15:52:32 +0100	[thread overview]
Message-ID: <YFyjsAtilH+3fggx@kroah.com> (raw)
In-Reply-To: <30ee6d6b-9206-acad-b224-591fdeb0dad7@siemens.com>

On Thu, Mar 25, 2021 at 03:46:10PM +0100, Jan Kiszka wrote:
> On 15.03.21 17:10, Rob Springer wrote:
> > Acked-by: Rob Springer <rspringer@google.com>
> > 
> > 
> > On Mon, Mar 15, 2021 at 8:44 AM <gregkh@linuxfoundation.org> wrote:
> >>
> >> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >>
> >> As none of the proposed things that need to be changed in the gasket
> >> drivers have ever been done, and there has not been any forward progress
> >> to get this out of staging, it seems totally abandonded so remove the
> >> code entirely so that people do not spend their time doing tiny cleanups
> >> for code that will never get out of staging.
> >>
> >> If this code is actually being used, it can be reverted simply and then
> >> cleaned up properly, but as it is abandoned, let's just get rid of it.
> >>
> >> Cc: Rob Springer <rspringer@google.com>
> >> Cc: Todd Poynor <toddpoynor@google.com>
> >> Cc: Ben Chan <benchan@chromium.org>
> >> Cc: Richard Yeh <rcy@google.com>
> >> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> OK, so is there a plan of the HW vendor to improve the user experience
> for this hardware? Is there a different software architecture in sight
> which will not need a kernel driver?

What hardware vendor makes this thing?  What systems require it?  And
why can't you use UIO instead?

> Just wondering loudly while fiddling with dkms packages and starring at
> the code diffs between what was removed here and what I still have to
> install manually from remote sources.

Where are the remote sources for this thing and why didn't they ever get
synced into the kernel tree?

thanks,

greg k-h

  reply	other threads:[~2021-03-25 14:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 15:44 [PATCH] staging: gasket: remove it from the kernel gregkh
2021-03-15 16:08 ` Rob Springer
2021-03-15 16:10 ` Rob Springer
2021-03-25 14:46   ` Jan Kiszka
2021-03-25 14:52     ` Greg KH [this message]
2021-03-25 14:57       ` Jan Kiszka

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=YFyjsAtilH+3fggx@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=benchan@chromium.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=rcy@google.com \
    --cc=rspringer@google.com \
    --cc=toddpoynor@google.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