From: David Miller <davem@davemloft.net>
To: roprabhu@cisco.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH] enic: Move enic port profile handling code to a new 802.1Qbh provisioning info type
Date: Fri, 10 Dec 2010 16:22:23 -0800 (PST) [thread overview]
Message-ID: <20101210.162223.216771509.davem@davemloft.net> (raw)
In-Reply-To: <20101210220233.5010.37181.stgit@savbu-pc100.cisco.com>
From: Roopa Prabhu <roprabhu@cisco.com>
Date: Fri, 10 Dec 2010 14:02:33 -0800
> From: Roopa Prabhu <roprabhu@cisco.com>
>
>
>
> Signed-off-by: Roopa Prabhu <roprabhu@cisco.com>
> Signed-off-by: David Wang <dwang2@cisco.com>
> Signed-off-by: Christian Benvenuti <benve@cisco.com>
Commit message could explain why you're doing this, but I'll
apply this as it is pretty simple.
prev parent reply other threads:[~2010-12-11 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 22:02 [net-next-2.6 PATCH] enic: Move enic port profile handling code to a new 802.1Qbh provisioning info type Roopa Prabhu
2010-12-11 0:22 ` David Miller [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=20101210.162223.216771509.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roprabhu@cisco.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).