Thread (43 messages) 43 messages, 3 authors, 2018-09-10

[PATCH v2 00/16] nvmem: rework of the subsystem for non-DT users

From: Bartosz Golaszewski <hidden>
Date: 2018-09-10 14:58:18
Also in: linux-doc, lkml

2018-09-10 12:02 GMT+02:00 Srinivas Kandagatla [off-list ref]:

On 10/09/18 09:24, Bartosz Golaszewski wrote:
quoted
The API changes change so many things, that these series would be
incompatible. I can send the series separately but they would be
co-dependent anyway. Does it sound good?

What am asking is to reorder the patches in a such a way that its easy to
review.
ex: Order can be :
1> kref and update nvmem_unregister followed by the provider changes.
2> Add support to cell tables, cell lookup, notifier
3> general cleanup patches  followed by fixes

Current set seems to jump from one thing to other which makes it hard to
follow and time consuming while review!
I would just change that ordering a bit: I think we should fix stuff
that's broken first, so fix the name field of struct nvmem_device,
then the rest as you listed it.

Bart
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help