Thread (22 messages) 22 messages, 4 authors, 2023-07-28

Re: [RFC PATCH v9 00/10] Create common DPLL configuration API

From: Jiri Pirko <jiri@resnulli.us>
Date: 2023-06-24 09:23:50
Also in: intel-wired-lan, linux-clk, linux-doc, linux-rdma, lkml

Fri, Jun 23, 2023 at 05:53:36PM CEST, kuba@kernel.org wrote:
On Fri, 23 Jun 2023 17:19:11 +0200 Jiri Pirko wrote:
quoted
I don't understand. The discussion in the RFCv8 thread is still going
on. The things I mentioned there are ignored. Like for example:
1) mode_set op removal
2) odd ice dpll locking scheme (either fix or describe why it is ok -
				that's the unfinished discussion)
3) header file bits squash I suggested. Vadim wrote that it sounds
   reasonable, yet nothing changed

I thought we are past this. Why I have to point the same issues over and
over?
FWIW I'm lost in the previous thread, so for me there's value in
refreshing the series.

But you're right, at the very least there should be a summary of
outstanding issues / open items / ongoing discussions in the cover
letter.
Well I would like to conclude discussion in one thread before sending
the next one. What should I do? Should I start the same discussion
pointing out the same issues in this thread again? This can't work.

Even concluded items are ignored, like 3)

IDK, this is very frustrating for me. I have to double check everything
just in case it was not ignored. I don't understand this, there is no
justification.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help