From: "Michael S. Tsirkin" <mst@redhat.com>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: john.r.fastabend@intel.com, netdev@vger.kernel.org,
shemminger@vyatta.com, bridge@lists.linux-foundation.org,
jhs@mojatatu.com
Subject: Re: [PATCH v2 net-next 1/8] bridge: Turn flag change macro into a function.
Date: Thu, 15 May 2014 20:18:22 +0300 [thread overview]
Message-ID: <20140515171822.GA1699@redhat.com> (raw)
In-Reply-To: <1400173016-8952-2-git-send-email-vyasevic@redhat.com>
On Thu, May 15, 2014 at 12:56:49PM -0400, Vlad Yasevich wrote:
> Turn the flag change macro into a function to allow
> easier updates and to reduce space.
>
> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
whitespace nit below
> ---
> net/bridge/br_sysfs_if.c | 27 +++++++++++++++++----------
> 1 file changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/net/bridge/br_sysfs_if.c b/net/bridge/br_sysfs_if.c
> index dd595bd..112a25e 100644
> --- a/net/bridge/br_sysfs_if.c
> +++ b/net/bridge/br_sysfs_if.c
> @@ -41,20 +41,27 @@ static ssize_t show_##_name(struct net_bridge_port *p, char *buf) \
> } \
> static int store_##_name(struct net_bridge_port *p, unsigned long v) \
> { \
> - unsigned long flags = p->flags; \
> - if (v) \
> - flags |= _mask; \
> - else \
> - flags &= ~_mask; \
> - if (flags != p->flags) { \
> - p->flags = flags; \
> - br_ifinfo_notify(RTM_NEWLINK, p); \
> - } \
> - return 0; \
> + return store_flag(p, v, _mask); \
> } \
> static BRPORT_ATTR(_name, S_IRUGO | S_IWUSR, \
> show_##_name, store_##_name)
>
> +static int store_flag(struct net_bridge_port *p, unsigned long v,
> + unsigned long mask)
This second line should align "unsigned" with "struct" on the line above
it. As it is it's aligned with ( which violates the docinf style
requirement
Descendants are always substantially shorter than the parent and
are placed substantially to the right.
it's not substantially to the right if it's not to the right of (.
> +{
> + unsigned long flags = p->flags;
> +
> + if (v)
> + flags |= mask;
> + else
> + flags &= ~mask;
> +
> + if (flags != p->flags) {
> + p->flags = flags;
> + br_ifinfo_notify(RTM_NEWLINK, p);
> + }
> + return 0;
> +}
>
> static ssize_t show_path_cost(struct net_bridge_port *p, char *buf)
> {
> --
> 1.9.0
next prev parent reply other threads:[~2014-05-15 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 16:56 [PATCH v2 net-next 0/8] Non-promisc bidge ports support Vlad Yasevich
2014-05-15 16:56 ` [PATCH v2 net-next 1/8] bridge: Turn flag change macro into a function Vlad Yasevich
2014-05-15 17:18 ` Michael S. Tsirkin [this message]
2014-05-15 16:56 ` [PATCH v2 net-next 2/8] bridge: Keep track of ports capable of automatic discovery Vlad Yasevich
2014-05-15 18:43 ` Michael S. Tsirkin
2014-05-15 16:56 ` [PATCH v2 net-next 3/8] bridge: Add functionality to sync static fdb entries to hw Vlad Yasevich
2014-05-15 18:43 ` Michael S. Tsirkin
2014-05-15 16:56 ` [PATCH v2 net-next 4/8] bridge: Introduce BR_PROMISC flag Vlad Yasevich
2014-05-15 18:44 ` Michael S. Tsirkin
2014-05-15 16:56 ` [PATCH v2 net-next 5/8] bridge: Add addresses from static fdbs to non-promisc ports Vlad Yasevich
2014-05-15 17:35 ` Michael S. Tsirkin
2014-05-15 16:56 ` [PATCH v2 net-next 6/8] bridge: Automatically manage port promiscuous mode Vlad Yasevich
2014-05-15 18:47 ` Michael S. Tsirkin
2014-05-15 16:56 ` [PATCH v2 net-next 7/8] bridge: Correctly manage promiscuity when user requested it Vlad Yasevich
2014-05-15 18:50 ` Michael S. Tsirkin
2014-05-15 16:56 ` [PATCH v2 net-next 8/8] bridge: Automatically manage promisc mode when vlan filtering is on Vlad Yasevich
2014-05-15 18:57 ` Michael S. Tsirkin
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=20140515171822.GA1699@redhat.com \
--to=mst@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=jhs@mojatatu.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=vyasevic@redhat.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).