linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Olaf Dabrunz <Olaf.Dabrunz@gmx.net>,
	Stefan Assmann <sassmann@redhat.com>,
	linux-kernel@vger.kernel.org, jcm@redhat.com,
	sdietrich@novell.com, linux-acpi@vger.kernel.org,
	andi@firstfloor.org, hpa@zytor.com, mingo@elte.hu,
	ktokunag@redhat.com, tglx@linutronix.de, lenb@kernel.org
Subject: Re: [RFC][PATCH 2/2] disable boot interrupts on Intel X58 and 55x0
Date: Sun, 06 Sep 2009 18:53:45 -0700	[thread overview]
Message-ID: <1252288425.2139.11.camel@desktop> (raw)
In-Reply-To: <20090907013742.GB19670@khazad-dum.debian.net>

On Sun, 2009-09-06 at 22:37 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 05 Sep 2009, Daniel Walker wrote:
> > I'm not sure I see how this makes "adding/deleting/modifying" easier ..
> > We have lots of other situations where lines are broken down less than
> > 80, function arguments, macros, structures all sorts of stuff. 
> > 
> > Taking this block for instance,
> > 
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_BROADCOM,
> >                         PCI_DEVICE_ID_TIGON3_5780,
> >                         quirk_msi_intx_disable_bug);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_BROADCOM,
> >                         PCI_DEVICE_ID_TIGON3_5780S,
> >                         quirk_msi_intx_disable_bug);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_BROADCOM,
> >                         PCI_DEVICE_ID_TIGON3_5714,
> >                         quirk_msi_intx_disable_bug);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_BROADCOM,
> >                         PCI_DEVICE_ID_TIGON3_5714S,
> >                         quirk_msx_intx_disable_bug);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_BROADCOM,
> >                         PCI_DEVICE_ID_TIGON3_5715,
> >                         quirk_msi_intx_disable_bug);
> > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_BROADCOM,
> >                         PCI_DEVICE_ID_TIGON3_5715S,
> >                         quirk_msi_intx_disable_bug);
> 
> You must have an alien brain of some sort if reading that is easier than the
> tabular (single-line) format for you.

My terminal isn't at 130 ..

> Please try finding the one entry in there which is different (I changed one
> of them) with a quick glance.  Chances are you'll just skip over it and
> think all of them do the same thing.

msix , the letters didn't line up, the semicolons don't line up either..
Even with tabs all this information is so similar your bound to overlook
small errors like that. Even if you think all this matter, assume
someone has a term at 80 then every thing is wrapper. That would put you
in the same situation. 

Daniel

Daniel


  reply	other threads:[~2009-09-07  1:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 16:55 [RFC][PATCH 0/2] boot interrupts on Intel X58 and 55x0 Stefan Assmann
2009-09-04 16:55 ` [RFC][PATCH 1/2] show Intel QuickPath Interconnect Routing and Protocol Layer Registers in PCI config space Stefan Assmann
2009-09-04 17:07   ` Yinghai Lu
2009-09-05  9:02     ` Stefan Assmann
2009-09-04 16:55 ` [RFC][PATCH 2/2] disable boot interrupts on Intel X58 and 55x0 Stefan Assmann
2009-09-04 17:06   ` Daniel Walker
2009-09-05  9:07     ` Stefan Assmann
2009-09-05 14:47       ` Daniel Walker
2009-09-05 16:18         ` Olaf Dabrunz
2009-09-05 17:07           ` Daniel Walker
2009-09-07  1:37             ` Henrique de Moraes Holschuh
2009-09-07  1:53               ` Daniel Walker [this message]
2009-09-07  1:33 ` [RFC][PATCH 0/2] " Henrique de Moraes Holschuh
2009-09-07  8:24   ` Stefan Assmann

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=1252288425.2139.11.camel@desktop \
    --to=dwalker@fifo99.com \
    --cc=Olaf.Dabrunz@gmx.net \
    --cc=andi@firstfloor.org \
    --cc=hmh@hmh.eng.br \
    --cc=hpa@zytor.com \
    --cc=jcm@redhat.com \
    --cc=ktokunag@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sassmann@redhat.com \
    --cc=sdietrich@novell.com \
    --cc=tglx@linutronix.de \
    /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).