From: Jeff Garzik <jeff@garzik•org>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: netdev@vger•kernel.org, Andy Fleming <afleming@freescale•com>
Subject: Re: [PATCH] Convert network devices to use struct device instead of class_device
Date: Sat, 17 Feb 2007 15:12:06 -0500 [thread overview]
Message-ID: <45D76196.6090708@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702140036350.855@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>
>
> ---
>
> Jeff,
>
> Sorry my mailer was completely screwed. I thought I had fixed the
> settings to turn of flowed text. I think this was why the patches I've
> been sending haven't been applying. You can also get this fix from the
> following git tree:
>
> master.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git gfar
pulled
next prev parent reply other threads:[~2007-02-17 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 6:40 [PATCH] Convert network devices to use struct device instead of class_device Kumar Gala
2007-02-14 19:40 ` Jeff Garzik
2007-02-17 20:12 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-08 17:08 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=45D76196.6090708@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=afleming@freescale$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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