From: Jakub Kicinski <kuba@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
o.rempel@pengutronix.de, p.zabel@pengutronix.de
Subject: Re: [PATCH net-next] net: ag71xx: update FIFO bits and descriptions
Date: Wed, 28 Aug 2024 15:29:27 -0700 [thread overview]
Message-ID: <20240828152927.6370bed2@kernel.org> (raw)
In-Reply-To: <20240828204251.6642-1-rosenp@gmail.com>
On Wed, 28 Aug 2024 13:42:49 -0700 Rosen Penev wrote:
> Taken from QCA SDK. No functional difference as same bits get applied.
Are these used? Would be nice to heave your best guess on the impact
this change will have in the commit message, for posterity scanning
git logs a few months/years from now.
BTW missing CC netdev, feel free to resend without 24h wait.
next prev parent reply other threads:[~2024-08-28 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 20:42 [PATCH net-next] net: ag71xx: update FIFO bits and descriptions Rosen Penev
2024-08-28 22:29 ` Jakub Kicinski [this message]
2024-08-28 22:36 ` Rosen Penev
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=20240828152927.6370bed2@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=o.rempel@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=rosenp@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