From: <Arun.Ramadoss@microchip.com>
To: <vtpieter@gmail.com>
Cc: <andrew@lunn.ch>, <olteanv@gmail.com>, <robh@kernel.org>,
<Woojung.Huh@microchip.com>, <pieter.van.trappen@cern.ch>,
<davem@davemloft.net>, <marex@denx.de>, <conor+dt@kernel.org>,
<edumazet@google.com>, <UNGLinuxDriver@microchip.com>,
<devicetree@vger.kernel.org>, <linux@armlinux.org.uk>,
<linux-kernel@vger.kernel.org>, <pabeni@redhat.com>,
<krzk+dt@kernel.org>, <kuba@kernel.org>, <netdev@vger.kernel.org>,
<f.fainelli@gmail.com>
Subject: Re: [PATCH net-next v4 5/5] net: dsa: microchip: apply KSZ87xx family fixes wrt datasheet
Date: Mon, 12 Aug 2024 14:29:49 +0000 [thread overview]
Message-ID: <039c9a99c890472bea5ca4e4a8abc0830fe7b607.camel@microchip.com> (raw)
In-Reply-To: <CAHvy4Aq8G2vLzFCCRRQV5kCD4jp8oYW+c=m_foyHXKoeiCod5A@mail.gmail.com>
On Mon, 2024-08-12 at 12:55 +0200, Pieter wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> Hi Arun,
>
> > @@ -141,7 +141,7 @@ static struct sk_buff *ksz8795_rcv(struct
> > sk_buff
> > > *skb, struct net_device *dev)
> > > {
> > > u8 *tag = skb_tail_pointer(skb) - KSZ_EGRESS_TAG_LEN;
> > >
> > > - return ksz_common_rcv(skb, dev, tag[0] & 7,
> > > KSZ_EGRESS_TAG_LEN);
> > > + return ksz_common_rcv(skb, dev, tag[0] & 3,
> > > KSZ_EGRESS_TAG_LEN);
> > > }
> >
> > This change can be separate patch. since it is not related to
> > ksz87xx_dev_ops structure. Is it a fix or just good to have one. If
> > it
> > is a fix then it should be point to net tree.
> >
>
> It's a fix wrt to datasheet but in reality I can see from tests with
> a KSZ8794 that bit 2 is always 0 so the bug doesn't manifest itself.
>
> Please advise, keep it in net-next or make a separate patch for the
> net tree?
Then it could point to net-next. Keep it as 6th patch of this patch
set. Instead of 3 as magic number, it can be macro.
prev parent reply other threads:[~2024-08-12 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:49 [PATCH net-next v4 0/5] net: dsa: microchip: ksz8795: add Wake on LAN support vtpieter
2024-08-12 8:49 ` [PATCH net-next v4 1/5] dt-bindings: net: dsa: microchip: add microchip,pme-active-high flag vtpieter
2024-08-12 8:49 ` [PATCH net-next v4 2/5] net: dsa: microchip: move KSZ9477 WoL functions to ksz_common vtpieter
2024-08-12 8:49 ` [PATCH net-next v4 3/5] net: dsa: microchip: generalize KSZ9477 WoL functions at ksz_common vtpieter
2024-08-12 8:49 ` [PATCH net-next v4 4/5] net: dsa: microchip: add WoL support for KSZ87xx family vtpieter
2024-08-12 10:39 ` Arun.Ramadoss
2024-08-12 8:49 ` [PATCH net-next v4 5/5] net: dsa: microchip: apply KSZ87xx family fixes wrt datasheet vtpieter
2024-08-12 10:45 ` Arun.Ramadoss
2024-08-12 10:55 ` Pieter
2024-08-12 14:29 ` Arun.Ramadoss [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=039c9a99c890472bea5ca4e4a8abc0830fe7b607.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pieter.van.trappen@cern.ch \
--cc=robh@kernel.org \
--cc=vtpieter@gmail.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
all inboxes | Powered by JetHome®