From: Pavan Chebbi <pavan.chebbi@broadcom.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux@armlinux.org.uk, vladimir.oltean@nxp.com,
pabeni@redhat.com, rogerq@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, vigneshr@ti.com,
spatton@ti.com
Subject: Re: [PATCH net] net: ethernet: ti: am65-cpsw: Fix RGMII configuration at SPEED_10
Date: Wed, 30 Nov 2022 11:26:39 +0530 [thread overview]
Message-ID: <CALs4sv2m0UaiJR2k-2+qaTQdeft8Edf2yN6jmu7=1OzHhDguNA@mail.gmail.com> (raw)
In-Reply-To: <c31f226f-dd6c-3235-ada3-6a69b66e156d@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 427 bytes --]
On Wed, Nov 30, 2022 at 10:54 AM Siddharth Vadapalli <s-vadapalli@ti.com> wrote:
>
> Hello,
>
> On 29/11/22 11:16, Pavan Chebbi wrote:
> > Looks like this patch should be directed to net-next?
>
> The commit fixed by this patch is a part of the released kernel. Thus, I
> think it should be a part of net instead of net-next. Please let me know.
>
Sorry, yes. Also you may want to respond to Vladimir.
> Regards,
> Siddharth.
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-30 5:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 5:06 [PATCH net] net: ethernet: ti: am65-cpsw: Fix RGMII configuration at SPEED_10 Siddharth Vadapalli
2022-11-29 5:46 ` Pavan Chebbi
2022-11-29 16:46 ` Vladimir Oltean
2022-11-30 5:59 ` Siddharth Vadapalli
2022-11-30 5:24 ` Siddharth Vadapalli
2022-11-30 5:56 ` Pavan Chebbi [this message]
2022-12-01 6:00 ` patchwork-bot+netdevbpf
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='CALs4sv2m0UaiJR2k-2+qaTQdeft8Edf2yN6jmu7=1OzHhDguNA@mail.gmail.com' \
--to=pavan.chebbi@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=spatton@ti.com \
--cc=vigneshr@ti.com \
--cc=vladimir.oltean@nxp.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).