From: David Miller <davem@davemloft.net>
To: privat@egil-hjelmeland.no
Cc: andrew@lunn.ch, vivien.didelot@savoirfairelinux.com,
f.fainelli@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: lan9303: Drop port range check
Date: Wed, 08 Nov 2017 13:44:30 +0900 (KST) [thread overview]
Message-ID: <20171108.134430.697082446447816114.davem@davemloft.net> (raw)
In-Reply-To: <20171106141949.19806-1-privat@egil-hjelmeland.no>
From: Egil Hjelmeland <privat@egil-hjelmeland.no>
Date: Mon, 6 Nov 2017 15:19:49 +0100
> Now that ds->num_ports is 3, there is no need to check range of "port"
> parameter.
>
> Signed-off-by: Egil Hjelmeland <privat@egil-hjelmeland.no>
Applied.
prev parent reply other threads:[~2017-11-08 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 14:19 [PATCH net-next] net: dsa: lan9303: Drop port range check Egil Hjelmeland
2017-11-06 14:39 ` Egil Hjelmeland
2017-11-08 4:44 ` 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=20171108.134430.697082446447816114.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=privat@egil-hjelmeland.no \
--cc=vivien.didelot@savoirfairelinux.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).