From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Anton Arapov <aarapov@redhat.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ip: justification for local port range robustness
Date: Thu, 18 Oct 2007 08:30:30 -0700 [thread overview]
Message-ID: <20071018083030.05a2aade@freepuppy.rosehill> (raw)
In-Reply-To: <m3odewh50m.fsf@bandura.englab.brq.redhat.com>
On Thu, 18 Oct 2007 16:27:37 +0200
Anton Arapov <aarapov@redhat.com> wrote:
> Hi!
>
> There is a justifying patch for Stephen's patches. Stephen's patches
> disallows using a port range of one single port and brakes the meaning
> of the 'remaining' variable, in some places it has different meaning.
> My patch gives back the sense of 'remaining' variable. It should mean how
> many ports are remaining and nothing else. Also my patch allows using
> a single port.
>
> I sure we must be able to use mentioned port range, this does not
> restricted by documentation and does not brake current behavior.
>
> usefull links:
> Patches posted by Stephen Hemminger
> http://marc.info/?l=linux-netdev&m=119206106218187&w=2
> http://marc.info/?l=linux-netdev&m=119206109918235&w=2
>
> Andrew Morton's comment
> http://marc.info/?l=linux-kernel&m=119248225007737&w=2
>
> == Patch:
>
> Justification of the Stephen Hemminger's patches, commit numbers
> 06393009000779b00a558fd2f280882cc7dc2008
> 227b60f5102cda4e4ab792b526a59c8cb20cd9f8
>
> 1. Allows using a port range of one single port.
> 2. Gives back sense of 'remaining' variable.
>
> Signed-off-by: Anton Arapov <aarapov@redhat.com>
Acked-by: Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-10-18 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 14:27 [PATCH] ip: justification for local port range robustness Anton Arapov
2007-10-18 15:30 ` Stephen Hemminger [this message]
2007-10-19 5:00 ` 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=20071018083030.05a2aade@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=aarapov@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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