netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Nault <g.nault@alphalink.fr>
To: tejaswit@codeaurora.org
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] slip: Check if rstate is initialized before uncompressing
Date: Tue, 10 Apr 2018 11:48:11 +0200	[thread overview]
Message-ID: <20180410094811.GA1433@alphalink.fr> (raw)
In-Reply-To: <ed7bd53914f26c2225c6c00d16bffb35@codeaurora.org>

On Tue, Apr 10, 2018 at 11:28:10AM +0530, tejaswit@codeaurora.org wrote:
> On 2018-04-09 20:34, David Miller wrote:
> > From: Tejaswi Tanikella <tejaswit@codeaurora.org>
> > Date: Mon, 9 Apr 2018 14:23:49 +0530
> > 
> > > @@ -673,6 +677,7 @@ struct slcompress *
> > >  	if (cs->cs_tcp.doff > 5)
> > >  	  memcpy(cs->cs_tcpopt, icp + ihl*4 + sizeof(struct tcphdr),
> > > (cs->cs_tcp.doff - 5) * 4);
> > >  	cs->cs_hsize = ihl*2 + cs->cs_tcp.doff*2;
> > > +	cs->initialized = 1;
> > >  	/* Put headers back on packet
> >  ...
> > >  struct cstate {
> > >  	byte_t	cs_this;	/* connection id number (xmit) */
> > > +	byte_t	initialized;	/* non-zero if initialized */
> > 
> > Please use 'bool' and true/false for 'initialized'.
> 
> Made the changes.

Hi Tejaswi,

Please send the new version of your patch as fresh new submission, with
proper subject prefix. In this case, it should be [PATCH net v2]. 'net'
because this is a bugfix and it should therefore target the 'net' tree.
'v2' because that's the second version of this series.

Also it'd be good if you could add a proper 'Fixes' tag in order to
help with stable backports. If the bug has always been there, just say
so.

I have no expertise on slhc, but overall, the patch content looks fine.

Guillaume

  reply	other threads:[~2018-04-10  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09  8:53 [PATCH] slip: Check if rstate is initialized before uncompressing Tejaswi Tanikella
2018-04-09 15:04 ` David Miller
2018-04-10  5:58   ` tejaswit
2018-04-10  9:48     ` Guillaume Nault [this message]
2018-04-10 14:03     ` David Miller

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=20180410094811.GA1433@alphalink.fr \
    --to=g.nault@alphalink.fr \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=tejaswit@codeaurora.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).