From: Jeff Garzik <jgarzik@pobox.com>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: netdev@vger.kernel.org,
Patrice Vilchez <patrice.vilchez@rfo.atmel.com>,
Andrew Victor <andrew@sanpeople.com>
Subject: Re: [PATCH] MACB: Use struct delayed_work instead of struct work_struct
Date: Mon, 11 Dec 2006 09:32:23 -0500 [thread overview]
Message-ID: <457D6BF7.6030707@pobox.com> (raw)
In-Reply-To: <20061208143735.7050553a@dhcp-252-105.norway.atmel.com>
Haavard Skinnemoen wrote:
> The macb driver calls schedule_delayed_work() and friends, so we need
> to use a struct delayed_work along with it. The conversion was
> explained by David Howells on lkml Dec 5 2006:
>
> http://lkml.org/lkml/2006/12/5/269
>
> Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
applied this, and the raw register access patch
prev parent reply other threads:[~2006-12-11 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 13:37 [PATCH] MACB: Use struct delayed_work instead of struct work_struct Haavard Skinnemoen
2006-12-08 13:38 ` [PATCH] MACB: Use __raw register access Haavard Skinnemoen
2006-12-11 14:32 ` Jeff Garzik [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=457D6BF7.6030707@pobox.com \
--to=jgarzik@pobox.com \
--cc=andrew@sanpeople.com \
--cc=hskinnemoen@atmel.com \
--cc=netdev@vger.kernel.org \
--cc=patrice.vilchez@rfo.atmel.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;
as well as URLs for NNTP newsgroup(s).