netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Schulz <develop@kristov.de>
To: Varka Bhadram <varkabhadram@gmail.com>,
	Daniel Borkmann <dborkman@redhat.com>
Cc: netdev@vger.kernel.org, linux-ppp@vger.kernel.org,
	paulus@samba.org, isdn@linux-pingi.de
Subject: Re: [PATCH net 1/1] net: ppp: fix creating PPP pass and active filters
Date: Tue, 15 Jul 2014 08:35:29 +0200	[thread overview]
Message-ID: <53C4CBB1.5000202@kristov.de> (raw)
In-Reply-To: <53C4B9BF.1020902@gmail.com>

Hello!

Am 15.07.2014 07:18, schrieb Varka Bhadram:
> There are can be two solutions:
> 
> 1. Replace the long function name (sk_unattached_filter_create) with the simple macro.
>     We can define the macro locally with our driver name.I don't know how many people
>     will accept it. For this we have to change the entire filter framework.
> 
> 2. Shorten the argument name 'pass_filter/active_filter'.
>     For this also we need to change the entire framework. People many not be accept it.

Is the 80 characters limit really that strong?
Documentation/SubmittingPatches contains the paragraph:

> The style checker should be viewed as
> a guide not as the final word.  If your code looks better with
> a violation then its probably best left alone.

IMHO defining and using local macros only to shorten two lines does not
improve code readability. Note that we talk about 83 and 85 characters,
respectively, not about >= 100.


Regards,

Christoph Schulz

  reply	other threads:[~2014-07-15  6:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 12:59 [PATCH net 1/1] net: ppp: fix creating PPP pass and active filters Christoph Schulz
2014-07-13 14:54 ` Varka Bhadram
2014-07-13 16:07   ` Christoph Schulz
2014-07-13 18:51     ` Daniel Borkmann
2014-07-15  4:54       ` Christoph Schulz
2014-07-15  5:18         ` Varka Bhadram
2014-07-15  6:35           ` Christoph Schulz [this message]
2014-07-15  6:59         ` Daniel Borkmann
2014-07-15 15:38           ` Alexei Starovoitov
2014-07-16 18:47             ` Christoph Schulz
2014-07-16 19:40               ` David Miller

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=53C4CBB1.5000202@kristov.de \
    --to=develop@kristov.de \
    --cc=dborkman@redhat.com \
    --cc=isdn@linux-pingi.de \
    --cc=linux-ppp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=varkabhadram@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;
as well as URLs for NNTP newsgroup(s).