From: Daniel Walker <dwalker@fifo99.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Yinghai Lu <yinghai@kernel.org>,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
ebiederm@xmission.com, akpm@linux-foundation.org, gregkh@suse.de,
tglx@linutronix.de, sarah.a.sharp@intel.com, mingo@elte.hu,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp
Date: Thu, 05 Mar 2009 15:44:54 -0800 [thread overview]
Message-ID: <1236296694.5937.107.camel@desktop> (raw)
In-Reply-To: <49B06327.5020307@oracle.com>
On Thu, 2009-03-05 at 15:41 -0800, Randy Dunlap wrote:
> If you have time to make a proposal for all such rules, please go ahead.
> I don't have time for it just now.
I don't know what kind of rules there are .. The 80 columns thing was
new to me.
> Yes, some examples, diagrams, samples, etc. are over 80 columns.
> It's not a diehard rule.
With code it sort of is die hard , even tho the CodingStyle doesn't
specify it that way.
Daniel
next prev parent reply other threads:[~2009-03-05 23:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090303235354.GA7145@gamba.jf.intel.com>
2009-03-04 1:31 ` EHCI debug documentation Yinghai Lu
2009-03-04 1:36 ` Randy Dunlap
2009-03-04 17:57 ` Ingo Molnar
2009-03-04 21:25 ` Greg KH
2009-03-04 21:39 ` Eric W. Biederman
2009-03-04 21:59 ` Alan Stern
2009-03-04 22:55 ` Sarah Sharp
2009-03-05 0:11 ` [PATCH] x86/doc: doc the using earlyprintk=dbgp Yinghai Lu
2009-03-05 10:00 ` [tip:x86/doc] x86/doc: mini-howto for " Yinghai Lu
2009-03-05 15:36 ` Daniel Walker
2009-03-05 19:22 ` Yinghai Lu
2009-03-05 22:40 ` Daniel Walker
2009-03-05 22:54 ` Alan Stern
2009-03-05 23:02 ` Daniel Walker
2009-03-05 23:05 ` Randy Dunlap
2009-03-05 23:12 ` Daniel Walker
2009-03-05 23:19 ` Randy Dunlap
2009-03-05 23:32 ` Daniel Walker
2009-03-05 23:41 ` Randy Dunlap
2009-03-05 23:44 ` Daniel Walker [this message]
2009-03-06 14:57 ` Alan Stern
2009-03-06 15:03 ` Daniel Walker
2009-03-06 15:55 ` Alan Stern
2009-03-05 23:48 ` Daniel Walker
2009-03-05 23:59 ` Randy Dunlap
2009-03-06 0:09 ` Daniel Walker
2009-03-06 15:52 ` Alan Stern
2009-03-06 15:55 ` Ingo Molnar
2009-03-06 16:16 ` Daniel Walker
2009-03-06 2:23 ` Daniel Walker
2009-03-05 2:06 ` EHCI debug documentation Greg KH
2009-03-04 22:50 ` Sarah Sharp
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=1236296694.5937.107.camel@desktop \
--to=dwalker@fifo99.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=sarah.a.sharp@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=yinghai@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.