On 18:10-20181210, Sekhar Nori wrote: > > I think you can rely on the author to tell you when something is > actually ready to be merged (and you can tell him/her to remind you). > > For the review itself, doing it by having a look at the dependencies > mentioned in the cover letter (like available for this series) should be > good enough (I feel). Dependencies can be for multiple things.. anyways, Sigh.. > I am not sure if there is a need to post an "RFC version", and then > follow it up with an actual "PATCH version" once dependencies are > cleared though. Heads up for the maintainers will be useful. For example: Will be good to state in cover-letter instead of just stating https://patchwork.kernel.org/cover/10717641/ State: Bindings are in discussion[2], will confirm if approved and will check if rebase is necessary. This will indicate to the maintainer that patches are preliminary and subject to change depending on bindings discussion and developer has taken ownership of maintaining patch sanity. -- Regards, Nishanth Menon
