Hi Jacopo, On Fri, Jan 15, 2021 at 10:03:26AM +0100, Jacopo Mondi wrote: > Ups, > > I'll fix. A question for Mauro though > > On Thu, Jan 14, 2021 at 02:20:34PM -0600, Rob Herring wrote: > > On Tue, Dec 22, 2020 at 3:50 AM Sakari Ailus > > <sakari.ailus@xxxxxxxxxxxxxxx> wrote: > > > > > > Hi Rob, > > > > > > On Mon, Dec 21, 2020 at 01:23:29PM -0700, Rob Herring wrote: > > > > On Wed, Nov 25, 2020 at 2:15 AM Sakari Ailus > > > > <sakari.ailus@xxxxxxxxxxxxxxx> wrote: > > > > > > > > > > Cc Rob + DT list. > > > > > > > > You have to resend if you really want me to see things. In this case, > > > > I don't think you need to wait on me for a rename. > > > > > > I merged the patch earlier based on the IRC discussion. > > > > Seems this landed in -next: > > > > ./Documentation/devicetree/bindings/media/i2c/ovti,ov5647.yaml: $id: > > relative path/filename doesn't match actual path or filename > > expected: http://devicetree.org/schemas/media/i2c/ovti,ov5647.yaml# > > > > The fix is worth a Fixes: tag, should I refer to the current commit > sha1 in linux-media/master or is there any risk for a rebase before > the tree is merged in the v5.12 merge window ? I'd say that happens only in exceptional circumstances. I think you can do that. -- Regards, Sakari Ailus
