From: Rob Herring <robh@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: "Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: net: brcm,amac: Allow "dma-coherent" property
Date: Fri, 19 Dec 2025 14:24:14 -0600 [thread overview]
Message-ID: <20251219202414.GA3873318-robh@kernel.org> (raw)
In-Reply-To: <982376c5-ad72-4923-9653-7f01c1e608a2@redhat.com>
On Fri, Dec 19, 2025 at 10:14:36AM +0100, Paolo Abeni wrote:
> Hi Rob,
>
> On 12/15/25 10:27 PM, Rob Herring (Arm) wrote:
> > The Broadcom AMAC controller is DMA coherent on some platforms, so allow
> > the dma-coherent property.
> >
> > Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
>
> I assume you are targeting net-next here?
Well, yes. I remember to add "net-next" about 50% of the time. Sigh.
> If so, please be aware that
> net-next is currently closed due to the winter break up to Jan 2.
> Otherwise feel free to take it via the device tree.
Okay, I'll just take it.
Rob
prev parent reply other threads:[~2025-12-19 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 21:27 [PATCH] dt-bindings: net: brcm,amac: Allow "dma-coherent" property Rob Herring (Arm)
2025-12-15 21:37 ` Florian Fainelli
2025-12-19 9:14 ` Paolo Abeni
2025-12-19 20:24 ` Rob Herring [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=20251219202414.GA3873318-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
/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).