From: Alan Cox <alan@linux.intel.com>
To: "Daniel Glöckner" <daniel-gl@gmx.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings
Date: Wed, 01 Mar 2017 22:26:06 +0000 [thread overview]
Message-ID: <1488407166.12062.4.camel@linux.intel.com> (raw)
In-Reply-To: <20170301215858.GA25346@minime.bse>
On Wed, 2017-03-01 at 22:58 +0100, Daniel Glöckner wrote:
> On Wed, Mar 01, 2017 at 06:30:17PM +0800, kbuild test robot wrote:
> >
> > drivers/staging/media/atomisp/i2c/imx/imx.c:2486:3-8: No need to
> > set .owner here. The core will do it.
> >
> > Remove .owner field if calls are used which set it automatically
> >
> > Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
> >
> > CC: Alan Cox <alan@linux.intel.com>
> > Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
>
>
> May I ask which repository this patch is based on?
It's a major clean up from internal code. For various reasons the
previous history of the code can't be exposed (the internal repository
we have contains code that can't go out of Intel for example).
> Does Intel finally attempt to upstream the atomisp driver?
That's the goal for the ISP 2 driver (Baytrail/T and later
Cherrytrail). I can't speak for longer term plans with ISP 3 and later
devices which currently don't have upstream drivers. There are some
bits of support in ISP2 for some of the odder phone platforms as well
but I don't have a way to test them or think anyone cares so plan to
drop those.
Alan
next prev parent reply other threads:[~2017-03-01 22:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201703011837.1R4zsbQi%fengguang.wu@intel.com>
2017-03-01 10:30 ` [PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 21:58 ` Daniel Glöckner
2017-03-01 22:26 ` Alan Cox [this message]
2017-03-01 22:44 ` Fengguang Wu
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` [PATCH] staging/atomisp: fix returnvar.cocci warnings kbuild test robot
2017-03-01 10:30 ` [PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-03-01 10:30 ` kbuild test robot
2017-03-01 10:30 ` [PATCH] staging/atomisp: fix returnvar.cocci warnings kbuild test robot
2017-03-01 10:30 ` [PATCH] staging/atomisp: fix semicolon.cocci warnings kbuild test robot
2017-03-01 10:30 ` kbuild test robot
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=1488407166.12062.4.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=daniel-gl@gmx.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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;
as well as URLs for NNTP newsgroup(s).