From: Sean Anderson <sean.anderson@seco.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
"David S . Miller" <davem@davemloft.net>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net v2] net: dpaa2-mac: Get serdes only for backplane links
Date: Thu, 23 Mar 2023 10:44:34 -0400 [thread overview]
Message-ID: <c93f3b1d-3fc8-ee1c-7a7b-5d3d4562f5f9@seco.com> (raw)
In-Reply-To: <20230322161026.5633f8d4@kernel.org>
On 3/22/23 19:10, Jakub Kicinski wrote:
> On Wed, 22 Mar 2023 15:52:23 -0400 Sean Anderson wrote:
>> I see this is marked as "changes requested" on patchwork. However,
>> as explained above, I do not think that the requested changes are
>> necessary. Please review the patch status.
>
> Let me document this, it keeps coming up. Patch incoming..
This is documented in the commit message. In fact, I got almost the same
response from Ioana the last time, made the same explanation, and
updated the commit message, but he did not respond to any further
emails. If I resend again, what will prevent that happening again? I am
doing my best to try and clarify this patch, but I am getting no
feedback. Nothing like "OK, Sean that makes sense to me, please put it
in the commit message" or "No, I don't think that's right because of
XYZ."
--Sean
next prev parent reply other threads:[~2023-03-23 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 0:31 Sean Anderson
2023-03-06 8:09 ` Ioana Ciornei
2023-03-06 16:13 ` Sean Anderson
2023-03-22 19:52 ` Sean Anderson
2023-03-22 23:10 ` Jakub Kicinski
2023-03-23 14:44 ` Sean Anderson [this message]
2023-03-23 15:27 ` Ioana Ciornei
2023-03-23 16:30 ` Sean Anderson
2023-03-24 13:07 ` Ioana Ciornei
2023-03-27 18:25 ` Sean Anderson
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=c93f3b1d-3fc8-ee1c-7a7b-5d3d4562f5f9@seco.com \
--to=sean.anderson@seco.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®