public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Fenghua Yu <fenghua.yu@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2/5] Itanium MC Error Injection Tool: Doc and sample application
Date: Mon, 11 Dec 2006 18:12:24 +0000	[thread overview]
Message-ID: <20061211181224.GB9731@linux-os.sc.intel.com> (raw)
In-Reply-To: <20061208161422.A1100@unix-os.sc.intel.com>

On Mon, Dec 11, 2006 at 03:17:26PM +0800, Zhang, Yanmin wrote:
> On Fri, 2006-12-08 at 16:14 -0800, Fenghua Yu wrote:
> > +		dbr6		: 1,
> > +		reserved	: 48;
> > +} resources_t;
> Is it better to move above definitions to file include/asm-ia64/pal.h?
> 
I'm trying to have the kernel driver as simple as possible and leave the complexity to application. Thus the kernel will be smaller, and needs less update. After all the structure of parameters is only useful for this specific procedure and not common structure for other kernel parts.

Currently the driver is dummy; it doesn't know the structure of the paratmers. All it does is to provide a thin interface to call the pal procedure.

By doing this, I hope we may end up to have a few fancy and complicated applications from the community. In the mean time, we have a small and stable kernel driver underneath.

Thanks.

-Fenghua

  parent reply	other threads:[~2006-12-11 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09  0:14 [PATCH 2/5] Itanium MC Error Injection Tool: Doc and sample application Fenghua Yu
2006-12-11  7:17 ` [PATCH 2/5] Itanium MC Error Injection Tool: Doc and sample Zhang, Yanmin
2006-12-11 18:12 ` Fenghua Yu [this message]
2006-12-11 19:57 ` [PATCH 2/5] Itanium MC Error Injection Tool: Doc and sample application Russ Anderson
2006-12-11 21:08 ` Fenghua Yu
2006-12-11 21:25 ` Fenghua Yu
2006-12-11 21:36 ` Luck, Tony

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=20061211181224.GB9731@linux-os.sc.intel.com \
    --to=fenghua.yu@intel.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox