From: YunQiang Su <wzssyqa@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paulburton@kernel.org>,
linux@roeck-us.net, dan.carpenter@oracle.com,
willy@infradead.org, devel@driverdev.osuosl.org,
linux-mips <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Re-instate octeon staging drivers
Date: Wed, 4 Mar 2020 09:48:46 +0800 [thread overview]
Message-ID: <CAKcpw6VczRuMC_KRzP6VRPeZPtmEpVOJE5Fc+JhDH4mWU7jUVg@mail.gmail.com> (raw)
In-Reply-To: <20200212215200.GA2367959@kroah.com>
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?
>
> greg k-h
--
YunQiang Su
next prev parent reply other threads:[~2020-03-04 1:48 UTC|newest]
Thread overview: 11+ 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 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 [this message]
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
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=CAKcpw6VczRuMC_KRzP6VRPeZPtmEpVOJE5Fc+JhDH4mWU7jUVg@mail.gmail.com \
--to=wzssyqa@gmail.com \
--cc=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=willy@infradead.org \
/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).