From: "Charles (Chas) Williams" <3chas3@gmail.com>
To: Tillmann Heidsieck <theidsieck@leenox.de>
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] atm: iphase: Fix misleading indention and return -ENOMEM on error
Date: Mon, 12 Oct 2015 15:28:55 +0000 [thread overview]
Message-ID: <1444663735.3494.58.camel@gmail.com> (raw)
In-Reply-To: <1444506439-10414-1-git-send-email-theidsieck@leenox.de>
On Sat, 2015-10-10 at 21:47 +0200, Tillmann Heidsieck wrote:
> this series fixes two of them. The if(); warning would require
> restructuring the code to a larger extend. Beyond this there remains a
> whooping number of > 2k checkpatch.pl warnings and errors each. Those
> can be grouped into
...
> Generally I would not mind cleaning all this up for those who have to
> make functional changes to the driver. However, I would like to know
> from the maintainers if such an afford would be welcome or not.
It doesn't bother me if you do this. I can review it.
WARNING: multiple messages have this Message-ID (diff)
From: "Charles (Chas) Williams" <3chas3@gmail.com>
To: Tillmann Heidsieck <theidsieck@leenox.de>
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] atm: iphase: Fix misleading indention and return -ENOMEM on error
Date: Mon, 12 Oct 2015 11:28:55 -0400 [thread overview]
Message-ID: <1444663735.3494.58.camel@gmail.com> (raw)
In-Reply-To: <1444506439-10414-1-git-send-email-theidsieck@leenox.de>
On Sat, 2015-10-10 at 21:47 +0200, Tillmann Heidsieck wrote:
> this series fixes two of them. The if(); warning would require
> restructuring the code to a larger extend. Beyond this there remains a
> whooping number of > 2k checkpatch.pl warnings and errors each. Those
> can be grouped into
...
> Generally I would not mind cleaning all this up for those who have to
> make functional changes to the driver. However, I would like to know
> from the maintainers if such an afford would be welcome or not.
It doesn't bother me if you do this. I can review it.
next prev parent reply other threads:[~2015-10-12 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 19:47 [PATCH 0/2] atm: iphase: Fix misleading indention and return -ENOMEM on error Tillmann Heidsieck
2015-10-10 19:47 ` Tillmann Heidsieck
2015-10-10 19:47 ` [PATCH 1/2] atm: iphase: return -ENOMEM instead of -1 in case of failed kmalloc() Tillmann Heidsieck
2015-10-10 19:47 ` Tillmann Heidsieck
2015-10-13 2:56 ` David Miller
2015-10-13 2:56 ` David Miller
2015-10-10 19:47 ` [PATCH 2/2] atm: iphase: fix misleading indention Tillmann Heidsieck
2015-10-10 19:47 ` Tillmann Heidsieck
2015-10-13 2:56 ` David Miller
2015-10-13 2:56 ` David Miller
2015-10-12 15:28 ` Charles (Chas) Williams [this message]
2015-10-12 15:28 ` [PATCH 0/2] atm: iphase: Fix misleading indention and return -ENOMEM on error Charles (Chas) Williams
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=1444663735.3494.58.camel@gmail.com \
--to=3chas3@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=theidsieck@leenox.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.