From: Jakub Kicinski <kuba@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: netdev-bot+sashiko@kernel.org, j.bhargav.u@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, tony@atomide.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
goledhruva@gmail.com, m-chawdhry@ti.com, daniel.baluta@gmail.com,
simona.toaca@nxp.com
Subject: Re: [v3] dt-bindings: net: ti,davinci-emac: Convert to DT schema
Date: Thu, 3 Sep 2026 16:09:21 -0700 [thread overview]
Message-ID: <20260903160921.547dabf4@kernel.org> (raw)
In-Reply-To: <33fe3846-eb8d-4b0b-9355-46388c1db2d3@kernel.org>
On Thu, 3 Sep 2026 17:22:54 +0200 Krzysztof Kozlowski wrote:
> On 03/09/2026 17:17, netdev-bot+sashiko@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 2 potential
> > issue(s) to consider:
>
> Jakub and other netdev folks,
>
> I got this week a lot of new netdev Sashiko emails on my mailbox. All of
> them escape filtering, because they do not use PATCH keyword. Can you
> please fix that? PATCH is essential... For now I will just add a filter
> to drop sashiko to dev null instead based on recipient, because I am not
> going to add filters classifying email as patch just because "From" is
> matching something.
Ugh, not the first time we have this bug either, sorry.
Should be fixed now.
next prev parent reply other threads:[~2026-09-03 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 0:15 [PATCH v3] dt-bindings: net: ti,davinci-emac: Convert to DT schema Bhargav Joshi
2026-09-03 15:17 ` [v3] " netdev-bot+sashiko
2026-09-03 15:22 ` Krzysztof Kozlowski
2026-09-03 23:09 ` Jakub Kicinski [this message]
2026-09-03 19:43 ` Bhargav Joshi
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=20260903160921.547dabf4@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=goledhruva@gmail.com \
--cc=j.bhargav.u@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=simona.toaca@nxp.com \
--cc=tony@atomide.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