From: Roland Dreier <rdreier@cisco.com>
To: Greg KH <gregkh@suse.de>
Cc: Jeff Garzik <jeff@garzik.org>, Divy Le Ray <divy@chelsio.com>,
Steve Wise <swise@opengridcomputing.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] cxgb3 - convert to user struct device instead of class_device
Date: Thu, 08 Feb 2007 13:31:10 -0800 [thread overview]
Message-ID: <adad54kwd41.fsf@cisco.com> (raw)
In-Reply-To: <20070208211911.GA20988@suse.de> (Greg KH's message of "Thu, 8 Feb 2007 13:19:11 -0800")
> But I think Jeff already has a patch in the queue that makes this very
> change :)
Really? I'm not sure I looked everywhere in Jeff's maze of git
branches but I didn't see anything obvious in netdev-2.6.git when I
looked before sending this.
- R.
next prev parent reply other threads:[~2007-02-08 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 20:41 [PATCH] cxgb3 - convert to user struct device instead of class_device Roland Dreier
2007-02-08 21:19 ` Greg KH
2007-02-08 21:31 ` Roland Dreier [this message]
2007-02-08 21:46 ` Jeff Garzik
2007-02-08 22:02 ` Roland Dreier
2007-02-08 23:48 ` Kumar Gala
2007-02-09 3:24 ` Divy Le Ray
2007-02-09 4:13 ` Roland Dreier
2007-02-09 5:21 ` Jeff Garzik
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=adad54kwd41.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=divy@chelsio.com \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.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 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.