From: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
To: Wang Shaoyan <stufever@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, wangshaoyan.pt@taobao.com,
linux-atm-general@lists.sourceforge.net
Subject: Re: [PATCH] ATM: Fix wrong usage of INIT_WORK
Date: Thu, 7 Jul 2011 08:29:59 -0400 [thread overview]
Message-ID: <20110707082959.7a579a29@thirdoffive.cmf.nrl.navy.mil> (raw)
In-Reply-To: <CANxBZFo_2P+hrjNDmvU0wai2CA7Ry3LJ9vk+pZ4ML1RR12LKTQ@mail.gmail.com>
On Thu, 7 Jul 2011 20:04:25 +0800
Wang Shaoyan <stufever@gmail.com> wrote:
> I just don't know whether the marco FILL_RX_POOLS_IN_BH is useful?
the macro doesnt seem to be useful in anyway. it can simply be
eliminated.
prev parent reply other threads:[~2011-07-07 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 11:51 [PATCH] ATM: Fix wrong usage of INIT_WORK stufever
2011-07-07 11:51 ` David Miller
2011-07-07 12:04 ` Wang Shaoyan
2011-07-07 12:10 ` David Miller
2011-07-07 12:29 ` chas williams - CONTRACTOR [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=20110707082959.7a579a29@thirdoffive.cmf.nrl.navy.mil \
--to=chas@cmf.nrl.navy.mil \
--cc=davem@davemloft.net \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=stufever@gmail.com \
--cc=wangshaoyan.pt@taobao.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).