From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> To: Sakari Ailus <sakari.ailus@iki.fi> Cc: mchehab@kernel.org, robh+dt@kernel.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, c.barrett@framos.com, a.brela@framos.com Subject: Re: [PATCH v4 2/2] media: i2c: Add IMX290 CMOS image sensor driver Date: Fri, 4 Oct 2019 15:49:02 +0530 [thread overview] Message-ID: <20191004101902.GA19685@mani> (raw) In-Reply-To: <20191004092336.GL896@valkosipuli.retiisi.org.uk> Hi Sakari, On Fri, Oct 04, 2019 at 12:23:36PM +0300, Sakari Ailus wrote: > Hi Manivannan, > > On Thu, Oct 03, 2019 at 03:25:03PM +0530, Manivannan Sadhasivam wrote: > > Add driver for Sony IMX290 CMOS image sensor driver. The driver only > > supports I2C interface for programming and MIPI CSI-2 for sensor output. > > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> > > Could you remove the unneeded ret variable from imx290_power_on() and > unneeded goto in the same function? > yep, sure. > The MAINTAINERS entry belongs to the first patch adding new files. > You mean the bindings patch? If then, sorry no. Usually the devicetree bindings belongs to a separate patch and that is what perferred by Rob. I prefer the MAINTAINERS entry in a separate patch but I've seen subsystems maintainers asking to squash it with the driver patch. But squashing it with bindings patch seems weird to me. Thanks, Mani > Then I think this is good. > > -- > Regards, > > Sakari Ailus
WARNING: multiple messages have this Message-ID (diff)
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> To: Sakari Ailus <sakari.ailus@iki.fi> Cc: devicetree@vger.kernel.org, c.barrett@framos.com, linux-kernel@vger.kernel.org, a.brela@framos.com, robh+dt@kernel.org, mchehab@kernel.org, linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org Subject: Re: [PATCH v4 2/2] media: i2c: Add IMX290 CMOS image sensor driver Date: Fri, 4 Oct 2019 15:49:02 +0530 [thread overview] Message-ID: <20191004101902.GA19685@mani> (raw) In-Reply-To: <20191004092336.GL896@valkosipuli.retiisi.org.uk> Hi Sakari, On Fri, Oct 04, 2019 at 12:23:36PM +0300, Sakari Ailus wrote: > Hi Manivannan, > > On Thu, Oct 03, 2019 at 03:25:03PM +0530, Manivannan Sadhasivam wrote: > > Add driver for Sony IMX290 CMOS image sensor driver. The driver only > > supports I2C interface for programming and MIPI CSI-2 for sensor output. > > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> > > Could you remove the unneeded ret variable from imx290_power_on() and > unneeded goto in the same function? > yep, sure. > The MAINTAINERS entry belongs to the first patch adding new files. > You mean the bindings patch? If then, sorry no. Usually the devicetree bindings belongs to a separate patch and that is what perferred by Rob. I prefer the MAINTAINERS entry in a separate patch but I've seen subsystems maintainers asking to squash it with the driver patch. But squashing it with bindings patch seems weird to me. Thanks, Mani > Then I think this is good. > > -- > Regards, > > Sakari Ailus _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-04 10:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-03 9:55 [PATCH v4 0/2] Add IMX290 CMOS image sensor support Manivannan Sadhasivam 2019-10-03 9:55 ` Manivannan Sadhasivam 2019-10-03 9:55 ` [PATCH v4 1/2] dt-bindings: media: i2c: Add IMX290 CMOS sensor binding Manivannan Sadhasivam 2019-10-03 9:55 ` Manivannan Sadhasivam 2019-10-03 9:55 ` [PATCH v4 2/2] media: i2c: Add IMX290 CMOS image sensor driver Manivannan Sadhasivam 2019-10-03 9:55 ` Manivannan Sadhasivam 2019-10-04 9:23 ` Sakari Ailus 2019-10-04 9:23 ` Sakari Ailus 2019-10-04 10:19 ` Manivannan Sadhasivam [this message] 2019-10-04 10:19 ` Manivannan Sadhasivam 2019-10-04 10:59 ` Sakari Ailus 2019-10-04 10:59 ` Sakari Ailus
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20191004101902.GA19685@mani \ --to=manivannan.sadhasivam@linaro.org \ --cc=a.brela@framos.com \ --cc=c.barrett@framos.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=mchehab@kernel.org \ --cc=robh+dt@kernel.org \ --cc=sakari.ailus@iki.fi \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.