From: David Miller <davem@davemloft.net>
To: develop@kristov.de
Cc: netdev@vger.kernel.org, linux-ppp@vger.kernel.org, paulus@samba.org
Subject: Re: [PATCH net-next 1/1] net: ppp: access ppp->nextseq only if CONFIG_PPP_MULTILINK is defined
Date: Wed, 16 Jul 2014 14:48:52 -0700 (PDT) [thread overview]
Message-ID: <20140716.144852.143826954917759282.davem@davemloft.net> (raw)
In-Reply-To: <53C6F186.30809@kristov.de>
From: Christoph Schulz <develop@kristov.de>
Date: Wed, 16 Jul 2014 23:41:26 +0200
> From: Christoph Schulz <develop@kristov.de>
>
> Commit d762d038497c9df51c19fcbe69b094b3bf8e5568 resets the counter holding the
> next sequence number for multilink PPP fragments to zero whenever the
> SC_MULTILINK flag is set. However, this counter only exists if
> CONFIG_PPP_MULTILINK is defined. Consequently, the new code has to be enclosed
> within #ifdef CONFIG_PPP_MULTILINK ... #endif.
>
> Signed-off-by: Christoph Schulz <develop@kristov.de>
Applied, thanks.
prev parent reply other threads:[~2014-07-16 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 21:41 [PATCH net-next 1/1] net: ppp: access ppp->nextseq only if CONFIG_PPP_MULTILINK is defined Christoph Schulz
2014-07-16 21:48 ` Sergei Shtylyov
2014-07-17 6:37 ` Christoph Schulz
2014-07-16 21:48 ` David Miller [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=20140716.144852.143826954917759282.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=develop@kristov.de \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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).