From: David Miller <davem@davemloft.net>
To: peter.korsgaard@barco.com
Cc: haavard.skinnemoen@atmel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] macb: allow reception of large (>1518 bytes) frames
Date: Wed, 07 Apr 2010 21:53:49 -0700 (PDT) [thread overview]
Message-ID: <20100407.215349.39367977.davem@davemloft.net> (raw)
In-Reply-To: <1270652389-5364-1-git-send-email-peter.korsgaard@barco.com>
From: Peter Korsgaard <peter.korsgaard@barco.com>
Date: Wed, 7 Apr 2010 16:59:49 +0200
> Enable BIG bit in the network configuration register, so the MAC doesn't
> reject big frames (E.G. when vlans are used).
>
> Signed-off-by: Peter Korsgaard <peter.korsgaard@barco.com>
Applied to net-next-2.6, thanks.
prev parent reply other threads:[~2010-04-08 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 14:59 [PATCH] macb: allow reception of large (>1518 bytes) frames Peter Korsgaard
2010-04-08 4:53 ` 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=20100407.215349.39367977.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.korsgaard@barco.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).