public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
	devel@driverdev.osuosl.org,
	"Branden Bonaby" <brandonbonaby94@gmail.com>,
	YueHaibing <yuehaibing@huawei.com>,
	"Paul Burton" <paulburton@kernel.org>,
	"Julia Lawall" <julia.lawall@lip6.fr>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Florian Westphal" <fw@strlen.de>,
	linux-kernel@vger.kernel.org,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	"Giovanni Gherdovich" <bobdc9664@seznam.cz>,
	"Sandro Volery" <sandro@volery.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Valery Ivanov" <ivalery111@gmail.com>,
	"Petr Štetiar" <ynezz@true.cz>,
	"David S. Miller" <davem@davemloft.net>,
	"Wambui Karuga" <wambui.karugax@gmail.com>
Subject: Re: [PATCH 1/2] staging: octeon: delete driver
Date: Wed, 11 Dec 2019 10:22:33 +0300	[thread overview]
Message-ID: <20191211072233.GB2070@kadam> (raw)
In-Reply-To: <20191210214848.GA5834@darkstar.musicnaut.iki.fi>

On Tue, Dec 10, 2019 at 11:48:49PM +0200, Aaro Koskinen wrote:
> On Tue, Dec 10, 2019 at 12:15:15PM -0800, Guenter Roeck wrote:
> > On Tue, Dec 10, 2019 at 09:46:59PM +0200, Aaro Koskinen wrote:
> > > On Tue, Dec 10, 2019 at 01:01:20PM +0100, Greg Kroah-Hartman wrote:
> > > > I have no idea :(
> > > 
> > > It's stated in the TODO file you are deleting (visible in your
> > > patch): "This driver is functional and supports Ethernet on
> > > OCTEON+/OCTEON2/OCTEON3 chips at least up to CN7030."
> > > 
> > > This includes e.g. some D-Link routers and Uniquiti EdgeRouters. You
> > > can check from /proc/cpuinfo if you are running on this MIPS SoC.
> > 
> > It also results in "mips:allmodconfig" build failures in mainline
> > and is for that reason being marked as BROKEN. Unfortunately,
> > misguided attempts to clean it up had the opposite effect.
> 
> This was because of stubs hack added by someone - people who do not run
> or care about the hardware can now break it for others with their
> silly x86 "compile test"s.

Compile tests are nice in theory for finding static analysis bugs but
often they introduce static checker false positives because we don't
initialize *param variables in the stub functions.

And those compat stubs in particular were a headache to review.  We
broke the build a couple times, but we *almost* broke the build a *lot*
of times...

regards,
dan carpenter


      parent reply	other threads:[~2019-12-11  7:24 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
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 [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=20191211072233.GB2070@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=bobdc9664@seznam.cz \
    --cc=brandonbonaby94@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=fw@strlen.de \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ivalery111@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=paulburton@kernel.org \
    --cc=sandro@volery.com \
    --cc=wambui.karugax@gmail.com \
    --cc=willy@infradead.org \
    --cc=ynezz@true.cz \
    --cc=yuehaibing@huawei.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