public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	holtmann@linux.intel.com, yi.zhu@intel.com,
	linux-kernel@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] firmware: Allocate firmware id dynamically
Date: Wed, 27 May 2009 08:04:35 -0700	[thread overview]
Message-ID: <20090527150435.GA31097@kroah.com> (raw)
In-Reply-To: <ac3eb2510905270130m752eb6bo767f7f3817cb1742@mail.gmail.com>

On Wed, May 27, 2009 at 10:30:19AM +0200, Kay Sievers wrote:
> On Wed, May 27, 2009 at 10:17, Samuel Ortiz <sameo@linux.intel.com> wrote:
> 
> >> next-20090526:samples/firmware_class/firmware_sample_firmware_class.c
> > Do I really need to fix this one too ?
> 
> I does not compile since ages, it is totally outdated and uses the
> long removed struct class_device. And we really don't need an example
> for firmware loading, I think. This file should just be deleted.

Yeah, I had plans to write it "properly", but it's at the end of my long
TODO list :(

I'll just go delete the thing instead.

thanks,

greg k-h

  reply	other threads:[~2009-05-27 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 14:04 [PATCH] firmware: Allocate firmware id dynamically Samuel Ortiz
2009-05-26 14:11 ` Kay Sievers
2009-05-26 20:23   ` Andrew Morton
2009-05-27  1:57     ` Stephen Rothwell
2009-05-27  8:17       ` Samuel Ortiz
2009-05-27  8:30         ` Kay Sievers
2009-05-27 15:04           ` Greg KH [this message]
2009-05-27  9:16         ` John W. Linville
2009-05-27  9:53           ` Samuel Ortiz
2009-05-27  6:19   ` Marcel Holtmann
2009-05-26 14:51 ` [PATCH] libertas: adapt for dynamic firmware id allocation John W. Linville
2009-05-26 17:02   ` Dan Williams

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=20090527150435.GA31097@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=holtmann@linux.intel.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sameo@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=yi.zhu@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