linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"wzssyqa@gmail.com" <wzssyqa@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"willy@infradead.org" <willy@infradead.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"shomeek@phoenicselectronics.com"
	<shomeek@phoenicselectronics.com>,
	"paulburton@kernel.org" <paulburton@kernel.org>
Subject: Re: [PATCH 0/6] Re-instate octeon staging drivers
Date: Wed, 4 Mar 2020 19:47:50 +0000	[thread overview]
Message-ID: <bae500e38d3c83f1a8e11a4e593587b6c2363988.camel@alliedtelesis.co.nz> (raw)
In-Reply-To: <20200304115038.GB1581141@kroah.com>

On Wed, 2020-03-04 at 12:50 +0100, Greg KH wrote:
> On Wed, Mar 04, 2020 at 06:25:34PM +0800, YunQiang Su wrote:
> > Greg KH <gregkh@linuxfoundation.org> 于2020年3月4日周三 下午2:39写道:
> > > 
> > > On Wed, Mar 04, 2020 at 09:48:46AM +0800, YunQiang Su wrote:
> > > > Greg KH <gregkh@linuxfoundation.org> 于2020年2月13日周四 上午5:52写道:
> > > > > 
> > > > > On Wed, Feb 05, 2020 at 01:11:10PM +1300, Chris Packham wrote:
> > > > > > This series re-instates the octeon drivers that were recently removed and
> > > > > > addresses the build issues that lead to that decision.
> > > > > > 
> > > > > > I've approached Cavium/Marvell about taking a more active interest in getting
> > > > > > the code out of staging and into their proper location. No reply on that (yet).
> > > > > 
> > > > > Good luck with talking to the companies, hopefully that will work.
> > > > > 
> > > > > Anyway, I've applied this series, thanks for this, let's see what breaks
> > > > > now :)
> > > > 
> > > > Did you meet any problem to merge Chris's patchset?
> > > 
> > > They are all in linux-next, so you can see for yourself :)
> > 
> > Thank you so much. I found it.
> > It is very important for Debian MIPS Ports as we are using some of
> > Octeon machines.
> 
> If it is so important, why is no one working on fixing these drivers up?
> 

I have had a reply from Marvell. They've contracted support for the old
Cavium Octeon designs out to an external company. I'm not sure that
means that we'll see some action on these drivers any time soon but at
least they're doing something.

      reply	other threads:[~2020-03-04 19:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05  0:11 [PATCH 0/6] Re-instate octeon staging drivers Chris Packham
2020-02-05  0:11 ` [PATCH 1/6] Revert "staging: octeon-usb: delete the octeon usb host controller driver" Chris Packham
2020-02-05  0:11 ` [PATCH 2/6] Revert "staging: octeon: delete driver" Chris Packham
2020-02-05  0:11 ` [PATCH 3/6] MIPS: octeon: remove typedef declaration for cvmx_wqe Chris Packham
2020-02-05  0:11 ` [PATCH 4/6] MIPS: octeon: remove typedef declaration for cvmx_helper_link_info Chris Packham
2020-02-05  0:11 ` [PATCH 5/6] MIPS: octeon: remove typedef declaration for cvmx_pko_command_word0 Chris Packham
2020-02-05  0:11 ` [PATCH 6/6] Revert "staging/octeon: Mark Ethernet driver as BROKEN" Chris Packham
2020-02-12 21:52 ` [PATCH 0/6] Re-instate octeon staging drivers Greg KH
2020-03-04  1:48   ` YunQiang Su
2020-03-04  6:39     ` Greg KH
2020-03-04 10:25       ` YunQiang Su
2020-03-04 11:50         ` Greg KH
2020-03-04 19:47           ` Chris Packham [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=bae500e38d3c83f1a8e11a4e593587b6c2363988.camel@alliedtelesis.co.nz \
    --to=chris.packham@alliedtelesis.co.nz \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=shomeek@phoenicselectronics.com \
    --cc=willy@infradead.org \
    --cc=wzssyqa@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;
as well as URLs for NNTP newsgroup(s).