From: Harini Katakam <harinikatakamlinux@gmail.com>
To: Harini Katakam <harini.katakam@xilinx.com>
Cc: nicolas.ferre@atmel.com, davem@davemloft.net,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
boris.brezillon@free-electrons.com,
alexandre.belloni@free-electrons.com, netdev@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
"michals@xilinx.com" <michals@xilinx.com>
Subject: Re: [net-next PATCH 3/3] net: macb: Add change_mtu callback with jumbo support
Date: Fri, 10 Apr 2015 15:05:28 +0530 [thread overview]
Message-ID: <CAFcVECLONoSV8riBHpkhJXrx39wtDLP2X7zx=C6jdXGuqw_vAg@mail.gmail.com> (raw)
In-Reply-To: <9376b508-694b-4582-8f2c-4e85e2bab2b5@BY2FFO11FD054.protection.gbl>
On Fri, Apr 10, 2015 at 2:47 PM, Harini Katakam
<harini.katakam@xilinx.com> wrote:
> Add macb_change_mtu callback; if jumbo frame support is present allow
> mtu size changes upto (jumbo max length allowed - headers).
>
> Signed-off-by: Harini Katakam <harinik@xilinx.com>
> Reviewed-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com>
> ---
> drivers/net/ethernet/cadence/macb.c | 26 +++++++++++++++++++++++++-
> 1 file changed, 25 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/cadence/macb.c b/drivers/net/ethernet/cadence/macb.c
> index 85de91d..33f3283 100644
> --- a/drivers/net/ethernet/cadence/macb.c
> +++ b/drivers/net/ethernet/cadence/macb.c
> @@ -54,6 +54,10 @@
> #define MACB_MAX_TX_LEN ((unsigned int)((1 << MACB_TX_FRMLEN_SIZE) - 1))
> #define GEM_MAX_TX_LEN ((unsigned int)((1 << GEM_TX_FRMLEN_SIZE) - 1))
>
> +#define GEM_MTU_MIN_SIZE 68
> +
> +#define GEM_ZYNQMP_JUMBO_MAX 10240
I'm sorry - this definition is in the wrong patch. I'll correct it and
send a v2.
Regards,
Harini
next prev parent reply other threads:[~2015-04-10 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1428657441-27710-1-git-send-email-harinik@xilinx.com>
2015-04-10 9:17 ` [net-next PATCH 2/3] net: macb: Add support for jumbo frames Harini Katakam
2015-04-10 9:17 ` [net-next PATCH 3/3] net: macb: Add change_mtu callback with jumbo support Harini Katakam
2015-04-10 9:35 ` Harini Katakam [this message]
2015-04-10 9:41 ` [net-next PATCH 1/3] devicetree: Add compatible string for Zynq Ultrascale MPSoC Michal Simek
[not found] ` <1428657441-27710-2-git-send-email-harinik@xilinx.com>
2015-04-10 9:50 ` [net-next PATCH 2/3] net: macb: Add support for jumbo frames Michal Simek
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='CAFcVECLONoSV8riBHpkhJXrx39wtDLP2X7zx=C6jdXGuqw_vAg@mail.gmail.com' \
--to=harinikatakamlinux@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=harini.katakam@xilinx.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michals@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=punnaia@xilinx.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).