linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] class device cleanup for fbdev
Date: Mon, 12 Feb 2007 11:46:39 -0800	[thread overview]
Message-ID: <20070212194639.GA789@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702071950110.9071@pentafluge.infradead.org>

On Wed, Feb 07, 2007 at 07:53:09PM +0000, James Simmons wrote:
> 
> Let me know if this is the right approach. This patch uses the class field 
> in struct device.

Yes, it looks like the correct thing to do.

thanks,

greg k-h

      reply	other threads:[~2007-02-12 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 19:53 [PATCH] class device cleanup for fbdev James Simmons
2007-02-12 19:46 ` Greg KH [this message]

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=20070212194639.GA789@kroah.com \
    --to=greg@kroah.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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 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).