From: Krzysztof Halasa <khc@pm.waw.pl>
To: Joe Perches <joe@perches.com>
Cc: Mark Lord <kernel@teksavvy.com>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 02/10] drivers/ata: Fix continuation line formats
Date: Thu, 04 Feb 2010 02:39:53 +0100 [thread overview]
Message-ID: <m3pr4lye1i.fsf@intrepid.localdomain> (raw)
In-Reply-To: <1265224535.24887.16.camel@Joe-Laptop.home> (Joe Perches's message of "Wed, 03 Feb 2010 11:15:35 -0800")
Joe Perches <joe@perches.com> writes:
> If it's ever agreed that all lines > 80 cols are OK or
> new args after column 80 are OK, then sure.
It's been already agreed they are OK for any code.
There is no problem with complexity there, is there?
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-02-04 1:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 7:22 [PATCH 00/10] Non-printk continuation line fixes Joe Perches
2010-02-02 7:22 ` [PATCH 02/10] drivers/ata: Fix continuation line formats Joe Perches
2010-02-03 17:21 ` Mark Lord
2010-02-03 17:25 ` Jeff Garzik
2010-02-07 15:10 ` Sergey Matyukevich
2010-02-03 19:15 ` Joe Perches
2010-02-04 1:39 ` Krzysztof Halasa [this message]
2010-02-04 3:36 ` Joe Perches
2010-02-04 4:59 ` Mark Lord
2010-02-04 5:13 ` Andrew Morton
2010-02-04 14:03 ` Mark Lord
2010-02-04 5:16 ` Joe Perches
2010-02-04 14:07 ` Mark Lord
2010-02-02 7:22 ` [PATCH 03/10] drivers/gpu/drm/i915/intel_bios.c: " Joe Perches
2010-02-02 7:22 ` [lm-sensors] [PATCH 04/10] drivers/hwmon/vt8231.c: Fix continuation Joe Perches
2010-02-02 7:22 ` [PATCH 04/10] drivers/hwmon/vt8231.c: Fix continuation line formats Joe Perches
2010-02-02 7:56 ` [lm-sensors] [PATCH 04/10] drivers/hwmon/vt8231.c: Fix Jean Delvare
2010-02-02 7:56 ` [lm-sensors] [PATCH 04/10] drivers/hwmon/vt8231.c: Fix continuation line formats Jean Delvare
2010-02-02 8:01 ` [lm-sensors] [PATCH 04/10] drivers/hwmon/vt8231.c: Fix Joe Perches
2010-02-02 8:01 ` [lm-sensors] [PATCH 04/10] drivers/hwmon/vt8231.c: Fix continuation line formats Joe Perches
2010-02-02 7:22 ` [PATCH 05/10] drivers/net/davinci_emac.c: " Joe Perches
2010-02-02 7:22 ` [PATCH 06/10] drivers/scsi/qla2xxx/qua_os.c: " Joe Perches
2010-02-02 7:22 ` [PATCH 07/10] drivers/spi/spi_s3c64xx.c: " Joe Perches
[not found] ` <bf8e8f72e7c2da124daebc9e96f1236e34badbca.1265095094.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2010-02-02 8:21 ` Grant Likely
2010-02-02 8:21 ` Grant Likely
2010-02-02 7:22 ` [PATCH 08/10] drivers/staging: " Joe Perches
2010-02-02 7:22 ` [PATCH 09/10] drivers/video/via: " Joe Perches
2010-02-02 7:22 ` Joe Perches
2010-02-03 22:36 ` Florian Tobias Schandinat
2010-02-03 22:36 ` Florian Tobias Schandinat
2010-02-02 7:22 ` [PATCH 10/10] sound/soc/s3c24xx/s2c-pcm.c: " Joe Perches
2010-02-02 11:40 ` Mark Brown
2010-02-02 11:40 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2010-02-02 7:22 [PATCH 01/10] arch/ia64: " Joe Perches
2010-02-02 7:22 ` Joe Perches
2010-02-02 7:22 ` Joe Perches
2010-02-07 11:43 ` Avi Kivity
2010-02-07 11:43 ` Avi Kivity
2010-02-07 11:43 ` Avi Kivity
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=m3pr4lye1i.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=jgarzik@pobox.com \
--cc=joe@perches.com \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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.