From: Marcelo <marcelo.leitner@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: vyasevich@gmail.com, nhorman@tuxdriver.com, davem@davemloft.net,
linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] sctp: Remove some redundant code
Date: Thu, 15 Sep 2016 17:19:39 -0300 [thread overview]
Message-ID: <20160915201939.GB3200@localhost.localdomain> (raw)
In-Reply-To: <28e1309f-a084-2090-ce2a-a43c013ddc8e@wanadoo.fr>
On Thu, Sep 15, 2016 at 09:32:18PM +0200, Christophe JAILLET wrote:
> Le 15/09/2016 à 19:34, Marcelo a écrit :
> > On Sun, Sep 04, 2016 at 11:38:13AM +0200, Christophe JAILLET wrote:
> > > In commit 311b21774f13 ("sctp: simplify sk_receive_queue locking"), a call
> > > to 'skb_queue_splice_tail_init()' has been made explicit. Previously it was
> > > hidden in 'sctp_skb_list_tail()'
> > >
> > > Now, the code around it looks redundant. The '_init()' part of
> > > 'skb_queue_splice_tail_init()' should alreday do the same.
> > >
> > > Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> > I just noticed you didn't include netdev@ in the destinations.
> >
> > Is your patch going to be tracked somewhere else? It's not showing up in
> > http://patchwork.ozlabs.org/project/netdev/list/?submitter=66309&state=*&q=&archive=&delegate=
> >
> My fault, get_maintainer lists netdev@ but I missed it.
>
> Should I resubmit or is it ok?
I guess you need to resubmit then, as it's not showing up in patchwork.
Marcelo
prev parent reply other threads:[~2016-09-15 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 9:38 [PATCH] sctp: Remove some redundant code Christophe JAILLET
2016-09-05 12:40 ` marcelo.leitner
2016-09-05 23:48 ` marcelo.leitner
2016-09-07 15:19 ` Neil Horman
2016-09-15 17:34 ` Marcelo
2016-09-15 19:32 ` Christophe JAILLET
2016-09-15 20:19 ` Marcelo [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=20160915201939.GB3200@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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).