From: David Miller <davem@davemloft.net>
To: andrew@lunn.ch
Cc: grygorii.strashko@ti.com, netdev@vger.kernel.org, nsekhar@ti.com,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: ti: cpsw: allow to configure min tx packet size
Date: Wed, 28 Nov 2018 17:22:12 -0800 (PST) [thread overview]
Message-ID: <20181128.172212.1033397162837638079.davem@davemloft.net> (raw)
In-Reply-To: <20181129002835.GB5037@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Thu, 29 Nov 2018 01:28:35 +0100
> On Wed, Nov 28, 2018 at 04:43:40PM -0600, Grygorii Strashko wrote:
>> Hi Andrew,
>>
>> On 11/28/18 4:02 PM, Andrew Lunn wrote:
>> >> This is dynamic configuration related to ALE VLAN entries and
>> >> I do not see the way to support its auto-detection with current driver,
>> >> unfortunately.
>> >
>> > I think you can subscribe to switchdev events which will tell you.
>>
>> Thanks a lot for your review and comments.
>>
>> Unfortunately, we still do not have switchdev in place, but i need to resolve
>> existing issue somehow. This patch is small, local to CPSW fix which can be
>> backported to stable. So, if possible, and no strong objection, could we proceed with it?
>
> Hi Grygorii
>
> David is the person who generally says no to kernel module
> parameters. You should ask him.
No module options.
You'll be stuck with it forever.
Sorry.
next prev parent reply other threads:[~2018-11-29 1:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 23:43 [PATCH] net: ethernet: ti: cpsw: allow to configure min tx packet size Grygorii Strashko
2018-11-26 2:27 ` Andrew Lunn
2018-11-28 1:27 ` Grygorii Strashko
2018-11-28 4:49 ` Andrew Lunn
2018-11-28 20:56 ` Grygorii Strashko
2018-11-28 22:02 ` Andrew Lunn
2018-11-28 22:43 ` Grygorii Strashko
2018-11-29 0:28 ` Andrew Lunn
2018-11-29 1:22 ` David Miller [this message]
2018-11-29 23:51 ` Grygorii Strashko
2018-11-29 13:05 ` Lad, Prabhakar
2018-11-29 12:24 ` David Laight
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=20181128.172212.1033397162837638079.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.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).