All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH][RESEND] gianfar: Convert network devices to use struct device instead of class_device
Date: Fri, 09 Feb 2007 16:10:47 -0500	[thread overview]
Message-ID: <45CCE357.3030203@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702081118090.29779@localhost.localdomain>

Kumar Gala wrote:
> Convert network devices to use struct device instead of class_device.  Greg
> missed this one in his cleanup path.
> 
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>

OK, but doesn't apply to torvalds/linux-2.6.git ...

	Jeff




  reply	other threads:[~2007-02-09 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 17:19 [PATCH][RESEND] gianfar: Convert network devices to use struct device instead of class_device Kumar Gala
2007-02-09 21:10 ` Jeff Garzik [this message]
2007-02-09 21:33   ` [PATCH][RESPIN] " Kumar Gala
2007-02-12 21:57     ` Andy Fleming
2007-02-13  5:55     ` [git patches] gianfar sysfs driver fix Kumar Gala

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=45CCE357.3030203@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=galak@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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.