From: David Daney <ddaney@caviumnetworks.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sakshi Bansal <sakshi.april5@gmail.com>,
<gregkh@linuxfoundation.org>, <aaro.koskinen@nokia.com>,
<ralf@linux-mips.org>, <david.daney@cavium.com>,
<paul.martin@codethink.co.uk>, <aybuke.147@gmail.com>,
<helen.fornazier@gmail.com>, <joe@perches.com>,
<okash.khawaja@gmail.com>, <janne.huttunen@nokia.com>,
<jamie.lawler@gmail.com>, <robertoxmed@gmail.com>,
<jtk54@cornell.edu>, <devel@driverdev.osuosl.org>,
<linux-kernel@vger.kernel.org>,
<outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH] staging: octeon: fixed few coding style warnings
Date: Wed, 14 Oct 2015 14:04:00 -0700 [thread overview]
Message-ID: <561EC340.8050304@caviumnetworks.com> (raw)
In-Reply-To: <6531068.KI8IQomEHc@wuerfel>
On 10/14/2015 01:58 PM, Arnd Bergmann wrote:
> On Wednesday 14 October 2015 08:47:44 David Daney wrote:
>> On 10/14/2015 07:06 AM, Sakshi Bansal wrote:
>>> Fixed allignment issues and line over 80 characters
>>
>> Use spell checking on 'allignment'
>>
>> But that is not the main problem with the patch...
>>
>>
>> You are changing things other than white space and comment formatting,
>> can you tell us on which platforms the patch was tested to verify that
>> you didn't break anything?
>
> In general a good advice, but for trivial whitespace or comment
> changes, this is normally not necessary. Compile-testing a patch
> as you say is normally expected, if only to avoid embarrassing
> complaints if it does break later.
>
> For drivers that are not enabled in the x86 allmodconfig, it sure
> helps to say something like "Compile-tested using MIPS cross toolchain
> from https://www.kernel.org/pub/tools/crosstool/". Even better would
> be to send a fix to decouple the driver from asm/octeon/*.h
> to make it build on all architectures, but that is much more work
> than I'd expect for a trivial patch.
There is no point in such a patch. We know, a priori, that there will
*never* be a non-MIPS system with this hardware.
David Daney
next prev parent reply other threads:[~2015-10-14 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 14:06 [PATCH] staging: octeon: fixed few coding style warnings Sakshi Bansal
2015-10-14 15:47 ` David Daney
[not found] ` <CAHqFf+uUJ4UjvVESkGf9Mqa000U0Ek7qEPwe8wZSvrY3XOzBvw@mail.gmail.com>
2015-10-14 15:57 ` David Daney
[not found] ` <CAHqFf+tUE6AhxRLPA89txFCUWSPDEVrYqCneA_jsDBgzGH+G_Q@mail.gmail.com>
2015-10-14 16:09 ` David Daney
2015-10-15 13:40 ` Dan Carpenter
2015-10-15 16:58 ` David Daney
2015-10-15 18:13 ` Dan Carpenter
2015-10-14 20:58 ` Arnd Bergmann
2015-10-14 21:04 ` David Daney [this message]
2015-10-14 21:32 ` Arnd Bergmann
2015-10-14 19:34 ` Aaro Koskinen
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=561EC340.8050304@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=aaro.koskinen@nokia.com \
--cc=arnd@arndb.de \
--cc=aybuke.147@gmail.com \
--cc=david.daney@cavium.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=helen.fornazier@gmail.com \
--cc=jamie.lawler@gmail.com \
--cc=janne.huttunen@nokia.com \
--cc=joe@perches.com \
--cc=jtk54@cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=okash.khawaja@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=paul.martin@codethink.co.uk \
--cc=ralf@linux-mips.org \
--cc=robertoxmed@gmail.com \
--cc=sakshi.april5@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