All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Liviu Dudau <Liviu.Dudau@arm.com>,
	linux-rockchip <linux-rockchip@lists.infradead.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] drm: Improve drm_of_component_probe() to correctly handle ports and remote ports.
Date: Mon, 16 Nov 2015 17:43:21 +0000	[thread overview]
Message-ID: <20151116174321.GR8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPj87rP_qPk0dKhLQDpFAsAqL2LxG=_5n+0KMRW=qEih4mBTJA@mail.gmail.com>

On Mon, Nov 16, 2015 at 05:32:05PM +0000, Daniel Stone wrote:
> On 16 November 2015 at 17:22, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Please sensibly wrap your messages.  Your lines are longer than 80
> > characters which makes it exceedingly difficult for some people to reply
> > to your very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very long lines without first reformatting
> > them manually - and why should they bother to reply if they have that
> > kind of additional work?  Thanks.
> 
> His lines are wrapped mostly at 80, but sometimes at 86, characters.
> You should probably look into fixing your MUA.

No.

Standard net etiquette is that email should be wrapped around 72
characters to give space for reply indentation to remain readable
on an 80 column screen. Most of my email replies are written on an
80 column screen.

Wrapping at 80+ characters is against proper net etiquette.

Same applies to GIT commits: wrap at around 72 characters to allow
them to be readable on an 80 column display.  Linus will hate you
if you don't.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-rockchip <linux-rockchip@lists.infradead.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] drm: Improve drm_of_component_probe() to correctly handle ports and remote ports.
Date: Mon, 16 Nov 2015 17:43:21 +0000	[thread overview]
Message-ID: <20151116174321.GR8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPj87rP_qPk0dKhLQDpFAsAqL2LxG=_5n+0KMRW=qEih4mBTJA@mail.gmail.com>

On Mon, Nov 16, 2015 at 05:32:05PM +0000, Daniel Stone wrote:
> On 16 November 2015 at 17:22, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Please sensibly wrap your messages.  Your lines are longer than 80
> > characters which makes it exceedingly difficult for some people to reply
> > to your very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very long lines without first reformatting
> > them manually - and why should they bother to reply if they have that
> > kind of additional work?  Thanks.
> 
> His lines are wrapped mostly at 80, but sometimes at 86, characters.
> You should probably look into fixing your MUA.

No.

Standard net etiquette is that email should be wrapped around 72
characters to give space for reply indentation to remain readable
on an 80 column screen. Most of my email replies are written on an
80 column screen.

Wrapping at 80+ characters is against proper net etiquette.

Same applies to GIT commits: wrap at around 72 characters to allow
them to be readable on an 80 column display.  Linus will hate you
if you don't.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] drm: Improve drm_of_component_probe() to correctly handle ports and remote ports.
Date: Mon, 16 Nov 2015 17:43:21 +0000	[thread overview]
Message-ID: <20151116174321.GR8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPj87rP_qPk0dKhLQDpFAsAqL2LxG=_5n+0KMRW=qEih4mBTJA@mail.gmail.com>

On Mon, Nov 16, 2015 at 05:32:05PM +0000, Daniel Stone wrote:
> On 16 November 2015 at 17:22, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Please sensibly wrap your messages.  Your lines are longer than 80
> > characters which makes it exceedingly difficult for some people to reply
> > to your very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very very very very very very very very very
> > very very very very very very long lines without first reformatting
> > them manually - and why should they bother to reply if they have that
> > kind of additional work?  Thanks.
> 
> His lines are wrapped mostly at 80, but sometimes at 86, characters.
> You should probably look into fixing your MUA.

No.

Standard net etiquette is that email should be wrapped around 72
characters to give space for reply indentation to remain readable
on an 80 column screen. Most of my email replies are written on an
80 column screen.

Wrapping at 80+ characters is against proper net etiquette.

Same applies to GIT commits: wrap at around 72 characters to allow
them to be readable on an 80 column display.  Linus will hate you
if you don't.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-11-16 17:43 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 14:44 [PATCH 0/2] Improve drm_of_component_probe() and move rockchip to use it Liviu Dudau
2015-11-16 14:44 ` Liviu Dudau
2015-11-16 14:44 ` Liviu Dudau
2015-11-16 14:44 ` [PATCH 1/2] drm: Improve drm_of_component_probe() to correctly handle ports and remote ports Liviu Dudau
2015-11-16 14:44   ` Liviu Dudau
2015-11-16 14:44   ` Liviu Dudau
2015-11-16 16:22   ` Russell King - ARM Linux
2015-11-16 16:22     ` Russell King - ARM Linux
2015-11-16 16:22     ` Russell King - ARM Linux
2015-11-16 16:49     ` Liviu Dudau
2015-11-16 16:49       ` Liviu Dudau
2015-11-16 17:22       ` Russell King - ARM Linux
2015-11-16 17:22         ` Russell King - ARM Linux
2015-11-16 17:22         ` Russell King - ARM Linux
2015-11-16 17:32         ` Daniel Stone
2015-11-16 17:32           ` Daniel Stone
2015-11-16 17:32           ` Daniel Stone
2015-11-16 17:43           ` Russell King - ARM Linux [this message]
2015-11-16 17:43             ` Russell King - ARM Linux
2015-11-16 17:43             ` Russell King - ARM Linux
2015-11-16 17:48             ` Daniel Stone
2015-11-16 17:48               ` Daniel Stone
2015-11-16 17:48               ` Daniel Stone
2015-11-16 17:53               ` Russell King - ARM Linux
2015-11-16 17:53                 ` Russell King - ARM Linux
2015-11-16 21:17         ` Liviu Dudau
2015-11-16 21:17           ` Liviu Dudau
2015-11-16 21:17           ` Liviu Dudau
2015-11-16 22:33           ` Russell King - ARM Linux
2015-11-16 22:33             ` Russell King - ARM Linux
2015-11-16 14:44 ` [PATCH 2/2] drm/rockchip: Convert the probe function to the generic drm_of_component_probe() Liviu Dudau
2015-11-16 14:44   ` Liviu Dudau
2015-11-16 14:44   ` Liviu Dudau
2015-11-16 16:30   ` Russell King - ARM Linux
2015-11-16 16:30     ` Russell King - ARM Linux
2015-11-16 16:30     ` Russell King - ARM Linux
2015-11-16 16:52     ` Liviu Dudau
2015-11-16 16:52       ` Liviu Dudau
2015-11-16 16:52       ` Liviu Dudau
2015-11-16 17:01       ` Heiko Stübner
2015-11-16 17:01         ` Heiko Stübner
2015-11-16 17:01         ` Heiko Stübner
2015-11-16 16:07 ` [PATCH 0/2] Improve drm_of_component_probe() and move rockchip to use it Heiko Stübner
2015-11-16 16:07   ` Heiko Stübner
2015-11-16 16:07   ` Heiko Stübner
2015-11-16 16:50   ` Liviu Dudau
2015-11-16 16:50     ` Liviu Dudau
2015-11-16 16:50     ` Liviu Dudau

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=20151116174321.GR8644@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=Liviu.Dudau@arm.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.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.