The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marcus Wolf <marcus.wolf@wolf-entwicklungen.de>
Cc: Rishabh Hardas <rishabhhardas@gmail.com>,
	colin.king@canonical.com, rjosephwright@gmail.com,
	Joe Perches <joe@perches.com>,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org
Subject: Re: [PATCH v2 1/4] staging: pi433: Style fix - Correct long lines
Date: Tue, 22 Aug 2017 13:43:31 +0300	[thread overview]
Message-ID: <20170822104331.sbx5la2oyafnr5qv@mwanda> (raw)
In-Reply-To: <1560259806.104565.1503397799301@ox.hosteurope.de>

I'm skeptical that these are the absolute platonic ideal of what the
code should look like...  You may be right that it's mathematically
impossible to make these lines more readable, but we can't really debate
alternate versions of this until someone sends us a patch.

regards,
dan carpenter

  reply	other threads:[~2017-08-22 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 11:50 [PATCH v2 0/4] staging: pi433: Rename camel case and other style issues Rishabh Hardas
2017-08-03 11:50 ` [PATCH v2 1/4] staging: pi433: Style fix - Correct long lines Rishabh Hardas
2017-08-15  0:42   ` Greg KH
2017-08-16  7:31   ` Dan Carpenter
2017-08-20  4:47     ` Joe Perches
2017-08-22  9:27       ` Rishabh Hardas
2017-08-22 10:03         ` Dan Carpenter
2017-08-22 10:29           ` Marcus Wolf
2017-08-22 10:43             ` Dan Carpenter [this message]
2017-08-03 11:50 ` [PATCH v2 2/4] staging: pi433: Change Comments Rishabh Hardas
2017-08-16  7:35   ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 3/4] staging: pi433: Renaming Enums Rishabh Hardas
2017-08-16  7:34   ` Dan Carpenter
2017-08-03 11:50 ` [PATCH v2 4/4] staging: pi433: Remove camel case variable names Rishabh Hardas

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=20170822104331.sbx5la2oyafnr5qv@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=colin.king@canonical.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus.wolf@wolf-entwicklungen.de \
    --cc=rishabhhardas@gmail.com \
    --cc=rjosephwright@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