From: Alexander Stein <alexander.stein@systec-electronic.com>
To: linux-kernel@vger.kernel.org
Cc: Moritz Fischer <moritz.fischer@ettus.com>,
nicolas.ferre@atmel.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] net: macb: Fix coding style issues
Date: Tue, 08 Mar 2016 08:06:43 +0100 [thread overview]
Message-ID: <1562860.N8xpQysp6D@ws-stein> (raw)
In-Reply-To: <1457367460-9123-1-git-send-email-moritz.fischer@ettus.com>
Hi,
On Monday 07 March 2016 08:17:36, Moritz Fischer wrote:
> this series deals with most of the checkpatch warnings
> generated for macb. There are two BUG_ON()'s that I didn't touch, yet,
> that were suggested by checkpatch, that I can address in a follow up
> commit if needed.
I think addressing those BUG_ON() warnings would be nice as they can affect a running system pretty bad.
Best regards,
Alexander
prev parent reply other threads:[~2016-03-08 7:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 16:17 [PATCH 0/3] net: macb: Fix coding style issues Moritz Fischer
2016-03-07 16:17 ` [PATCH 1/3] net: macb: Fix coding style error message Moritz Fischer
2016-03-07 16:17 ` [PATCH 2/3] net: macb: Fix more coding style issues Moritz Fischer
2016-03-07 17:25 ` Joe Perches
2016-03-07 18:49 ` David Miller
2016-03-07 19:47 ` Moritz Fischer
2016-03-07 16:17 ` [PATCH 3/3] net: macb: Address checkpatch 'check' suggestions Moritz Fischer
2016-03-07 16:17 ` [PATCH 3/3] net: macb: Cleanup checkpatch checks Moritz Fischer
2016-03-07 16:19 ` Moritz Fischer
2016-03-07 17:13 ` [PATCH 0/3] net: macb: Fix coding style issues Nicolas Ferre
2016-03-09 16:29 ` Michal Simek
2016-03-09 17:18 ` Moritz Fischer
2016-03-09 17:22 ` David Miller
2016-03-09 17:29 ` Michal Simek
2016-03-09 20:26 ` David Miller
2016-03-08 7:06 ` Alexander Stein [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=1562860.N8xpQysp6D@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.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