From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/6] cnic: Unify kcq allocation for all devices.
Date: Fri, 25 Jun 2010 21:07:19 -0700 (PDT) [thread overview]
Message-ID: <20100625.210719.91322533.davem@davemloft.net> (raw)
In-Reply-To: <1277427522-17306-3-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Thu, 24 Jun 2010 17:58:39 -0700
> By creating a common data stucture kcq_info for all devices, the kcq
> (kernel completion queue) for all devices can be allocated by common
> code.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Applied.
next prev parent reply other threads:[~2010-06-26 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 0:58 [PATCH net-next 1/6] cnic: Fine-tune CID memory space calculation Michael Chan
2010-06-25 0:58 ` [PATCH net-next 2/6] cnic: Unify IRQ code for all hardware types Michael Chan
2010-06-25 0:58 ` [PATCH net-next 3/6] cnic: Unify kcq allocation for all devices Michael Chan
2010-06-25 0:58 ` [PATCH net-next 4/6] cnic: Restructure kcq processing Michael Chan
2010-06-25 0:58 ` [PATCH net-next 5/6] cnic: Further unify kcq handling code Michael Chan
2010-06-25 0:58 ` [PATCH net-next 6/6] cnic: Update version to 2.1.3 Michael Chan
2010-06-26 4:08 ` David Miller
2010-06-26 4:07 ` [PATCH net-next 5/6] cnic: Further unify kcq handling code David Miller
2010-06-26 4:07 ` [PATCH net-next 4/6] cnic: Restructure kcq processing David Miller
2010-06-26 4:07 ` David Miller [this message]
2010-06-26 4:07 ` [PATCH net-next 2/6] cnic: Unify IRQ code for all hardware types David Miller
2010-06-26 4:06 ` [PATCH net-next 1/6] cnic: Fine-tune CID memory space calculation David Miller
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=20100625.210719.91322533.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--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 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).