[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPv3WKfW+V+dohsqcM7OLm3EBTqM9v-_96=Bkfu-BKoJV7Ss=g@mail.gmail.com>
Date: Sun, 22 Nov 2015 22:55:03 +0100
From: Marcin Wojtas <mw@...ihalf.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Andrew Lunn <andrew@...n.ch>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Jason Cooper <jason@...edaemon.net>, netdev@...r.kernel.org,
Simon Guinot <simon.guinot@...uanux.org>,
linux-kernel@...r.kernel.org, Evan Wang <xswang@...vell.com>,
nadavh@...vell.com, nitroshift@...oo.com,
Lior Amsalem <alior@...vell.com>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Grzegorz Jaszczyk <jaz@...ihalf.com>,
Gregory Clément
<gregory.clement@...e-electrons.com>,
Tomasz Nowicki <tn@...ihalf.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Yair Mahalalel <myair@...vell.com>
Subject: Re: [PATCH 02/13] net: mvneta: enable IP checksum with jumbo frames
for Armada 38x on Port0
Arnd,
>
> If the feature set depends on the port number, we should think about
> the way it gets handled again, as this is probably better not described
> as something that depends (just) on the SoC, but on the way it gets
> integrated. Maybe we can introduce an additional property for the
> checksums on jumbo frames and use that if present but fall back to
> identifying by compatible string otherwise.
>
I think adding a property, taking also compatible strings will be the
best solution.
Best regards,
Marcin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists