All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Pan, Jacob jun" <jacob.jun.pan@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH 2/9] x86: introduce a set of platform feature flags
Date: Fri, 26 Jun 2009 12:47:03 +0200	[thread overview]
Message-ID: <20090626104703.GA12446@elte.hu> (raw)
In-Reply-To: <20090626111731.539f963e@lxorguk.ukuu.org.uk>


* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > Which bit is not clear? We've been continuously 'driverizing' 
> > the
> 
> What do you mean by "driverizing". You keep using your made up 
> word but since nobody else knows what you mean its not productive 
> to have the discussion using invented terms like that.

Yeah, it's a made up shortcut for "turning previously monolithic 
code into structured, driver-alike code with a driver data 
structure, possible data fields and function callbacks". See the x86 
examples i cited.

	Ingo

  reply	other threads:[~2009-06-26 10:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  0:14 [PATCH 2/9] x86: introduce a set of platform feature flags Pan, Jacob jun
2009-06-26  7:22 ` Ingo Molnar
2009-06-26  9:14   ` Alan Cox
2009-06-26  9:45     ` Ingo Molnar
2009-06-26 10:17       ` Alan Cox
2009-06-26 10:47         ` Ingo Molnar [this message]
2009-06-26 11:41           ` Alan Cox
2009-06-26 15:47 ` Ingo Molnar
2009-06-26 19:04   ` H. Peter Anvin
2009-06-26 19:13     ` Ingo Molnar
2009-06-30  6:32 ` Pavel Machek
2009-07-02 23:09   ` Pan, Jacob jun
2009-07-02 23:25     ` H. Peter Anvin

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=20090626104703.GA12446@elte.hu \
    --to=mingo@elte.hu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@linux.intel.com \
    --cc=jacob.jun.pan@intel.com \
    --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.