All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>, John Heenan <john@zgus.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] rtl8xxxu: Fix for bogus data used to determine macpower
Date: Thu, 03 Nov 2016 01:41:37 -0700	[thread overview]
Message-ID: <1478162497.1924.16.camel@perches.com> (raw)
In-Reply-To: <wrfjzillsan3.fsf@redhat.com>

On Sun, 2016-10-30 at 19:02 -0400, Jes Sorensen wrote:
> Code is 80 characters wide, and comments are /* */ never the ugly C++
> crap.

You might look at the recent Linus Torvalds authored commit
5e467652ffef (?printk: re-organize log_output() to be more legible")
which does both of those: c99 // comments and > 80 columns.

Absolutes are for zealots.

  reply	other threads:[~2016-11-03  8:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1477769750.git.john@zgus.com>
2016-10-30 10:20 ` [PATCH 1/2] rtl8xxxu: Fix for authentication failure John Heenan
2016-11-03  1:00   ` Larry Finger
2016-11-03  7:10     ` John Heenan
2016-11-03  7:10       ` John Heenan
2016-11-03  7:10       ` John Heenan
2016-11-03 15:39       ` Larry Finger
2016-10-30 10:21 ` [PATCH 2/2] rtl8xxxu: Fix for bogus data used to determine macpower John Heenan
2016-10-30 12:00   ` Jes Sorensen
2016-10-30 12:00     ` Jes Sorensen
2016-10-30 13:56     ` John Heenan
2016-10-30 23:02       ` Jes Sorensen
2016-11-03  8:41         ` Joe Perches [this message]
2016-11-03 15:43           ` Larry Finger
2016-11-04 13:56           ` Jes Sorensen
2016-11-04 13:56             ` Jes Sorensen
2016-11-03  1:00   ` Larry Finger
2016-11-03  2:58     ` David Miller
     [not found] <CANf5e8aQ+HZz47M3-4+qjsG=ZCaXhBFU_jVupLqT4rEYT2LQFQ@mail.gmail.com>
2016-11-08 14:29 ` Jes Sorensen
2016-11-10 22:45   ` Barry Day
2016-11-10 22:45     ` Barry Day

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=1478162497.1924.16.camel@perches.com \
    --to=joe@perches.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=john@zgus.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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.