From: Dan Carpenter <dan.carpenter@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"ddaney.cavm@gmail.com" <ddaney.cavm@gmail.com>,
"pundirsumit11@gmail.com" <pundirsumit11@gmail.com>,
"aaro.koskinen@iki.fi" <aaro.koskinen@iki.fi>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nishkadg.linux@gmail.com" <nishkadg.linux@gmail.com>,
"frank@generalsoftwareinc.com" <frank@generalsoftwareinc.com>,
"laura.lazzati.15@gmail.com" <laura.lazzati.15@gmail.com>
Subject: Re: [PATCH 2/2] staging: octeon-usb: delete the octeon usb host controller driver
Date: Tue, 4 Feb 2020 10:21:22 +0300 [thread overview]
Message-ID: <20200204072122.GR1778@kadam> (raw)
In-Reply-To: <20200204071548.GB966981@kroah.com>
My advice is to delete all the COMPILE_TEST code. That stuff was a
constant source of confusion and headaches.
regards,
dan carpenter
next prev parent reply other threads:[~2020-02-04 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 [this message]
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=20200204072122.GR1778@kadam \
--to=dan.carpenter@oracle.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=aaro.koskinen@iki.fi \
--cc=ddaney.cavm@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=frank@generalsoftwareinc.com \
--cc=gregkh@linuxfoundation.org \
--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