On Tue, Jul 12, 2022 at 08:21:27PM +0100, Marc Zyngier wrote: > On Tue, 12 Jul 2022 19:19:16 +0100, > Rob Herring <robh@xxxxxxxxxx> wrote: > > > > On Thu, Jul 07, 2022 at 10:51:33AM +0100, Marc Zyngier wrote: > > > > > Can you please have a look at the latest instance[1][2] of this > > > series, as posted by Samuel? I've provisionally queued it, but only on > > > the provision that you would eventually ack these patches. > > > > I did already[1]. They passed checks, were already in linux-next, and I > > didn't see anything major needing comments, so I marked it N/A (meaning > > someone else applies it) without comment. > > > > Rob > > > > [1] https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20220630100241.35233-2-samuel@xxxxxxxxxxxx/ > > How are people supposed to track this if it doesn't appear on the ML? Look at patchwork? How am I supposed to track maintainers that will rebase what they have in next to add acks and those that won't? > That's not really an ack, AFAICT. That's a "I don't care". I still look at it, so really it's an implicit ack. In this case, I probably just saw the irqchip-bot mail and missed your reply to the cover. > Does it mean I'm free to take any random DT patch unless you or a bot > shouts? I'd rather know. Wait for acked/reviewed-by to apply? Isn't that the process? Rob
