public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: devel@driverdev.osuosl.org,
	Sumit Pundir <pundirsumit11@gmail.com>,
	linux-kernel@vger.kernel.org, David Daney <ddaney.cavm@gmail.com>,
	Nishka Dasgupta <nishkadg.linux@gmail.com>,
	"Frank A. Cancio Bello" <frank@generalsoftwareinc.com>,
	Laura Lazzati <laura.lazzati.15@gmail.com>
Subject: Re: [PATCH 2/2] staging: octeon-usb: delete the octeon usb host controller driver
Date: Wed, 11 Dec 2019 08:42:18 +0100	[thread overview]
Message-ID: <20191211074218.GB398293@kroah.com> (raw)
In-Reply-To: <20191210212744.GD18225@darkstar.musicnaut.iki.fi>

On Tue, Dec 10, 2019 at 11:27:44PM +0200, Aaro Koskinen wrote:
> On Tue, Dec 10, 2019 at 09:19:57PM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Dec 10, 2019 at 09:31:54PM +0200, Aaro Koskinen wrote:
> > > Hi,
> > > 
> > > On Tue, Dec 10, 2019 at 10:15:09AM +0100, Greg Kroah-Hartman wrote:
> > > > This driver was merged back in 2013 and shows no progress toward every
> > > > being merged into the "correct" part of the kernel.
> > > 
> > > Do you mean all the patches since 2013 were "no progress"? Thanks.
> > 
> > I have not seen any proposals to get it out of staging at all.  If the
> > only thing left really is just those two simple TODO lines, then why has
> > it taken 6 years to do that?
> 
> Do you mean you did not see the below thread when I asked for help;
> it was a kind of propsal, no? Also things take time when you are just a
> hobbyist reverse engineering undocumented hardware that you also run in
> production. Yes, I'm slow, but the starting point wasn't also a very good.
> 
> https://marc.info/?t=155839354700002&r=1&w=2

I have the short-term memory of a squirrel, remember I get 1000 emails a
day to deal with.

That thread was from back in May, the instructions on what was needed to
be done is quite simple, so there should not have been a multi-month
delay from then until now.  What happened?

> I don't mind you deleting the driver, and if you think that "no progress"
> is true then I'm very sorry for all those commits/noise.

Don't be sorry, you have fixed it up to make it ready to be merged
properly.  But yes, there is no progress being made now, so it should
either be dropped or merged properly.

If you don't have the time now to do it, that's fine, the revert to get
the code back just takes one single git command when you, or someone
else, can get the chance to do it.

Don't take it personally, this is about to happen to almost all of the
staging drivers that have been languishing around :)

thanks,

greg k-h

  reply	other threads:[~2019-12-11  7:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  9:15 [PATCH 1/2] staging: octeon: delete driver Greg Kroah-Hartman
2019-12-10  9:15 ` [PATCH 2/2] staging: octeon-usb: delete the octeon usb host controller driver Greg Kroah-Hartman
2019-12-10 19:31   ` Aaro Koskinen
2019-12-10 20:19     ` Greg Kroah-Hartman
2019-12-10 21:27       ` Aaro Koskinen
2019-12-11  7:42         ` Greg Kroah-Hartman [this message]
2020-02-04  4:06   ` Chris Packham
2020-02-04  7:15     ` gregkh
2020-02-04  7:21       ` Dan Carpenter
2019-12-10 10:42 ` [PATCH 1/2] staging: octeon: delete driver Guenter Roeck
2020-02-04  4:02   ` Chris Packham
2020-02-04  7:09     ` gregkh
2020-02-04 20:06       ` Chris Packham
2020-02-04 20:31         ` Matthew Wilcox
2020-02-04 22:53           ` gregkh
2020-02-05  3:34           ` Dan Carpenter
2020-02-05  3:44             ` Matthew Wilcox
2020-02-05  3:56             ` Guenter Roeck
2020-02-05  9:03               ` Geert Uytterhoeven
2020-02-05 13:52                 ` Guenter Roeck
2020-02-06  8:18                   ` Geert Uytterhoeven
2019-12-10 11:40 ` Sandro Volery
2019-12-10 12:01   ` Greg Kroah-Hartman
2019-12-10 12:54     ` Sandro Volery
2019-12-10 19:46     ` Aaro Koskinen
2019-12-10 20:15       ` Guenter Roeck
2019-12-10 21:48         ` Aaro Koskinen
2019-12-10 22:48           ` Guenter Roeck
2019-12-11  7:22           ` Dan Carpenter

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=20191211074218.GB398293@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=ddaney.cavm@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=frank@generalsoftwareinc.com \
    --cc=laura.lazzati.15@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nishkadg.linux@gmail.com \
    --cc=pundirsumit11@gmail.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