From: Manivannan Sadhasivam <mani@kernel.org>
To: Sricharan Ramabadhran <quic_srichara@quicinc.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-arm-msm@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] net: qrtr: Do not do DEL_SERVER broadcast after DEL_CLIENT
Date: Fri, 31 Mar 2023 23:59:31 +0530 [thread overview]
Message-ID: <20230331182931.GB6352@thinkpad> (raw)
In-Reply-To: <4792f5c8-2902-2e46-b663-22cffe450556@quicinc.com>
On Fri, Mar 31, 2023 at 02:02:04PM +0530, Sricharan Ramabadhran wrote:
> <..>
>
> > > -static int server_del(struct qrtr_node *node, unsigned int port)
> > > +static int server_del(struct qrtr_node *node, unsigned int port, bool bcast)
> > > {
> > > struct qrtr_lookup *lookup;
> > > struct qrtr_server *srv;
> > > @@ -287,7 +287,7 @@ static int server_del(struct qrtr_node *node, unsigned int port)
> > > radix_tree_delete(&node->servers, port);
> > > /* Broadcast the removal of local servers */
> > > - if (srv->node == qrtr_ns.local_node)
> > > + if (srv->node == qrtr_ns.local_node && bcast)
> > > service_announce_del(&qrtr_ns.bcast_sq, srv);
> > > /* Announce the service's disappearance to observers */
> > > @@ -373,7 +373,7 @@ static int ctrl_cmd_bye(struct sockaddr_qrtr *from)
> > > }
> > > slot = radix_tree_iter_resume(slot, &iter);
> > > rcu_read_unlock();
> > > - server_del(node, srv->port);
> > > + server_del(node, srv->port, true);
> > > rcu_read_lock();
> > > }
> > > rcu_read_unlock();
> > > @@ -459,10 +459,13 @@ static int ctrl_cmd_del_client(struct sockaddr_qrtr *from,
> > > kfree(lookup);
> > > }
> > > - /* Remove the server belonging to this port */
> > > + /* Remove the server belonging to this port but don't broadcast
> >
> > This is still not as per the multi line comment style perferred in kernel.
> > Please read: https://www.kernel.org/doc/html/latest/process/coding-style.html#commenting
> >
>
> Ho, i had it like first style and checkpatch cribbed. Then changed it
> as per the second style for net/ format. You mean we should stick to
> 1 st style ?
>
Oops, sorry I forgot the fact that the networking code uses a different style.
Ignore my above comment.
- Mani
> Regards,
> Sricharan
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-03-31 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 7:48 [PATCH V2] net: qrtr: Do not do DEL_SERVER broadcast after DEL_CLIENT Sricharan Ramabadhran
2023-03-31 8:02 ` Manivannan Sadhasivam
2023-03-31 8:32 ` Sricharan Ramabadhran
2023-03-31 18:29 ` Manivannan Sadhasivam [this message]
2023-03-31 19:46 ` Simon Horman
2023-03-31 18:30 ` Manivannan Sadhasivam
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=20230331182931.GB6352@thinkpad \
--to=mani@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_srichara@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.