From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: vipul-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org,
divy-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org,
dm-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org,
kumaras-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org,
swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org,
abhishek-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org
Subject: Re: [PATCH V3 1/5] cxgb4: Add T4 filter support
Date: Mon, 03 Dec 2012 14:02:07 -0500 (EST) [thread overview]
Message-ID: <20121203.140207.164096621247746195.davem@davemloft.net> (raw)
In-Reply-To: <1354533781-31575-2-git-send-email-vipul-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
From: Vipul Pandya <vipul-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Date: Mon, 3 Dec 2012 16:52:57 +0530
> + /*
> + * If the new or old filter have loopback rewriteing rules then we'll
> + * need to free any existing Layer Two Table (L2T) entries of the old
> + * filter rule. The firmware will handle freeing up any Source MAC
> + * Table (SMT) entries used for rewriting Source MAC Addresses in
> + * loopback rules.
> + */
> + if (f->l2t)
> + cxgb4_l2t_release(f->l2t);
> +
> + /* The zeroing of the filter rule below clears the filter valid,
> + * pending, locked flags, l2t pointer, etc. so it's all we need for
> + * this operation.
> + */
My greatest amusement is achieved when someone gets a code formatting
rule both correct and wrong in the same patch, as you have done here.
Format comments in the networking:
/* Like
* this.
*/
/*
* Never,
* like this.
*/
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-12-03 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 11:22 [PATCH V3 0/5] Add LE hash collision bug fix for active and passive offloaded connections Vipul Pandya
[not found] ` <1354533781-31575-1-git-send-email-vipul-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2012-12-03 11:22 ` [PATCH V3 1/5] cxgb4: Add T4 filter support Vipul Pandya
[not found] ` <1354533781-31575-2-git-send-email-vipul-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2012-12-03 19:02 ` David Miller [this message]
2012-12-10 9:46 ` Vipul Pandya
2012-12-03 11:22 ` [PATCH V3 2/5] cxgb4: Add LE hash collision bug fix path in LLD driver Vipul Pandya
2012-12-03 11:22 ` [PATCH V3 3/5] RDMA/cxgb4: Fix LE hash collision bug for active open connection Vipul Pandya
2012-12-03 11:23 ` [PATCH V3 4/5] RDMA/cxgb4: Fix LE hash collision bug for passive " Vipul Pandya
2012-12-03 11:23 ` [PATCH V3 5/5] RDMA/cxgb4: Fix bug for active and passive LE hash collision path Vipul Pandya
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=20121203.140207.164096621247746195.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=abhishek-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=divy-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=dm-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=kumaras-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
--cc=vipul-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.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).