From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Devid Antonio Filoni <d.filoni@ubuntu.com>,
Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Alan Cox" <alan@linux.intel.com>,
"Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: atomisp: add a driver for ov5648 camera sensor
Date: Mon, 18 Sep 2017 10:26:22 +0300 [thread overview]
Message-ID: <1505719582.25945.271.camel@linux.intel.com> (raw)
In-Reply-To: <20170911180303.GA14304@dfiloni-N82JQ>
On Mon, 2017-09-11 at 20:03 +0200, Devid Antonio Filoni wrote:
> On Mon, Sep 11, 2017 at 05:55:29PM +0300, Sakari Ailus wrote:
> > Hi Devid,
> >
> > Please see my comments below.
> >
> > Andy: please look for "INT5648".
>
> Hi Sakari,
> I'm replying below to your comments. I'll work on a v2 patch as soon
> as we get
> more comments.
>
> About "INT5648", I extracted it from the DSDT of my Lenovo Miix 310,
> take a look
> at https://pastebin.com/ExHWYr8g .
First of all, thank you, Sakari, to raise a flag here.
Second, Devid, please answer to the following:
is it an official BIOS which is available in the wild?
If it's so, please, add a paragraph to the commit message explaining how do you get this and point to the DSDT excerpt.
Put an answer to above question to the commit message as well.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-09-18 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 12:23 [PATCH] staging: atomisp: add a driver for ov5648 camera sensor Devid Antonio Floni
2017-09-11 14:55 ` Sakari Ailus
2017-09-11 18:03 ` Devid Antonio Filoni
2017-09-18 7:26 ` Andy Shevchenko [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=1505719582.25945.271.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=d.filoni@ubuntu.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy.lefaure@lse.epita.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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: link
Be 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.