From: Jakub Kicinski <kuba@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Bhadram Varka <vbhadram@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 9/9] stmmac: tegra: Add MGBE support
Date: Fri, 23 Sep 2022 05:52:34 -0700 [thread overview]
Message-ID: <20220923055234.4714c86a@kernel.org> (raw)
In-Reply-To: <Yy2pFfUWU7LwGG/m@orome>
On Fri, 23 Sep 2022 14:39:49 +0200 Thierry Reding wrote:
> > Could you repost it independently of the series so that it can go thru
> > the net auto-checkers? It should be able to make 6.1 pretty comfortably.
>
> Done. Let me know if there's anything in the patch that needs more work.
> For the auto-checkers, do they send out notifications if they find
> anything or can I monitor them manually somewhere? Are all of those
> reported in the patchwork checks?
They are reported to patchwork, but they sometimes produce false
positives so we don't expect folks to look at the themselves. The
maintainers will reply to the submission and quote the failed checks
as needed.
Also note that we have a "at most one version per day" policy,
if, say, there is a build issue discovered please hold off posting
the new version for 24h. Frequent posting makes reviewing harder
for folks who read the list top to bottom and increases ML traffic.
prev parent reply other threads:[~2022-09-23 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 7:48 [PATCH v4 0/9] tegra: Add support for MGBE controller Thierry Reding
2022-07-07 7:48 ` [PATCH v4 1/9] dt-bindings: power: Add Tegra234 MGBE power domains Thierry Reding
2022-07-07 7:48 ` [PATCH v4 2/9] dt-bindings: Add Tegra234 MGBE clocks and resets Thierry Reding
2022-07-07 7:48 ` [PATCH v4 3/9] dt-bindings: memory: Add Tegra234 MGBE memory clients Thierry Reding
2022-07-07 7:48 ` [PATCH v4 4/9] memory: tegra: Add MGBE memory clients for Tegra234 Thierry Reding
2022-07-07 7:48 ` [PATCH v4 5/9] dt-bindings: net: Add Tegra234 MGBE Thierry Reding
2022-07-08 16:26 ` Thierry Reding
2022-07-11 19:09 ` Rob Herring
2022-07-07 7:48 ` [PATCH v4 6/9] arm64: tegra: Add MGBE nodes on Tegra234 Thierry Reding
2022-07-07 7:48 ` [PATCH v4 7/9] arm64: tegra: Enable MGBE on Jetson AGX Orin Developer Kit Thierry Reding
2022-07-07 7:48 ` [PATCH v4 8/9] arm64: defconfig: Enable Tegra MGBE driver Thierry Reding
2022-07-07 7:48 ` [PATCH net-next v4 9/9] stmmac: tegra: Add MGBE support Thierry Reding
2022-09-07 16:36 ` Thierry Reding
2022-09-22 15:05 ` Jon Hunter
2022-09-22 15:34 ` Jakub Kicinski
2022-09-23 12:39 ` Thierry Reding
2022-09-23 12:52 ` Jakub Kicinski [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=20220923055234.4714c86a@kernel.org \
--to=kuba@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vbhadram@nvidia.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).