public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH 1/1] sun6i-mipi-csi2: Depend on PHY_SUN6I_MIPI_DPHY
Date: Fri, 9 Sep 2022 16:41:31 +0200	[thread overview]
Message-ID: <YxtQm37sI84KR98M@aptenodytes> (raw)
In-Reply-To: <YxtPZpA1YBRgjBA3@paasikivi.fi.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

Hi Sakari,

On Fri 09 Sep 22, 14:36, Sakari Ailus wrote:
> Hi Paul,
> 
> On Fri, Sep 09, 2022 at 04:00:37PM +0200, Paul Kocialkowski wrote:
> > Hi Sakari,
> > 
> > On Mon 05 Sep 22, 13:00, Sakari Ailus wrote:
> > > PHY_SUN6I_MIPI_DPHY is not a freely selectable option and so may not
> > > always be available. Depend on it instead.
> > 
> > I don't get what you mean by "not a freely selectable option".
> > It's definitely a tristate. Also no build issue will occur if it's
> > unselected (but I guess that's not the point here).
> 
> It depends on a number of other configuration options. You can force the
> value of the option itself but not its dependencies. This can lead to build
> errors dependin on the values of the options PHY_SUN6I_MIPI_DPHY needs.

Ah yes I see, it's the usual issue with select selecting the option regardless
of its dependencies. My bad.

Reviewed-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>

Thanks,

Paul

-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2022-09-09 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 10:00 [PATCH 1/1] sun6i-mipi-csi2: Depend on PHY_SUN6I_MIPI_DPHY Sakari Ailus
2022-09-09 14:00 ` Paul Kocialkowski
2022-09-09 14:36   ` Sakari Ailus
2022-09-09 14:41     ` Paul Kocialkowski [this message]

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=YxtQm37sI84KR98M@aptenodytes \
    --to=paul.kocialkowski@bootlin.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox