From: Dan Carpenter <dan.carpenter@oracle.com>
To: Antonio Quartulli <antonio@meshcoding.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] question about min_t() casting in batadv_hardif_min_mtu()
Date: Tue, 4 Feb 2014 00:16:15 +0300 [thread overview]
Message-ID: <20140203211615.GC26776@mwanda> (raw)
In-Reply-To: <52EA5AAB.8080101@meshcoding.com>
On Thu, Jan 30, 2014 at 02:59:07PM +0100, Antonio Quartulli wrote:
>
> But why don't dev_set_mtu() check for the argument to be larger than
> 68bytes? Isn't that a general requirement?
I'm not a networking person. It sounds reasonable to me that we could
use add a better minimum check there but why is it 68 bytes?
regards,
dan carpenter
prev parent reply other threads:[~2014-02-03 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 12:52 [B.A.T.M.A.N.] question about min_t() casting in batadv_hardif_min_mtu() Dan Carpenter
2014-01-30 13:59 ` Antonio Quartulli
2014-02-03 21:16 ` Dan Carpenter [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=20140203211615.GC26776@mwanda \
--to=dan.carpenter@oracle.com \
--cc=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.