public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: David Vrabel <dvrabel@cantab.net>,
	long <tlnguyen@snoqualmie.dp.intel.com>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	greg@kroah.com
Subject: Re: [PATCH 1/6] PCI Express Advanced Error Reporting Driver
Date: Mon, 14 Mar 2005 09:00:35 -0800	[thread overview]
Message-ID: <4235C333.4060006@osdl.org> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E50240803A13E@orsmsx404.amr.corp.intel.com>

Nguyen, Tom L wrote:
> Monday, March 14, 2005 3:01 AM David Vrabel wrote:
> 
> 
>>>This patch includes PCIEAER-HOWTO.txt, which describes how the PCI
>>>Express Advanced Error Reporting Root driver works.
>>>
>>>--- linux-2.6.11-rc5/Documentation/PCIEAER-HOWTO.txt
>>>
>>
>>Could this be placed in a sub-system subdirectory (creating one if
>>necessary, e.g., pci/)?  The root of Documentation/ is rather full of
>>random files as is.
> 
> 
> Most of the HOWTO documents are under Documentation/ directory. I have
> no problem of placing it in a sub-system subdirectory if it is OK with
> Linux community?

It should remain in the Documentation/ directory or a (new)
subdirectory under Documentation/ .

-- 
~Randy

  reply	other threads:[~2005-03-14 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 16:54 [PATCH 1/6] PCI Express Advanced Error Reporting Driver Nguyen, Tom L
2005-03-14 17:00 ` Randy.Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-15 23:59 Nguyen, Tom L
2005-03-14 20:01 Nguyen, Tom L
2005-03-12  0:12 long
2005-03-12  9:37 ` Andi Kleen
2005-03-14 11:00 ` David Vrabel
2005-03-15 22:51 ` Linas Vepstas
2005-03-15 23:12   ` Grant Grundler

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=4235C333.4060006@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=dvrabel@cantab.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=tlnguyen@snoqualmie.dp.intel.com \
    --cc=tom.l.nguyen@intel.com \
    /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