From: jacopo mondi <jacopo@jmondi.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com,
mchehab@kernel.org, ysato@users.sourceforge.jp, dalias@libc.org,
linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Remove sh_mobile_ceu_camera from arch/sh
Date: Tue, 04 Sep 2018 09:33:58 +0000 [thread overview]
Message-ID: <20180904093358.GK20333@w540> (raw)
In-Reply-To: <20180903072234.GA4116@w540>
[-- Attachment #1: Type: text/plain, Size: 2265 bytes --]
Hi again Sakari,
sorry, I'm confusing you
On Mon, Sep 03, 2018 at 09:22:34AM +0200, jacopo mondi wrote:
> Hi Sakari,
>
> On Fri, Aug 31, 2018 at 03:25:58PM +0300, Sakari Ailus wrote:
> > Hi Jacopo,
> >
> > On Mon, May 28, 2018 at 06:37:06PM +0200, Jacopo Mondi wrote:
> > > Hello,
> > > this series removes dependencies on the soc_camera based
> > > sh_mobile_ceu_camera driver from 3 board files in arch/sh and from one
> > > sensor driver used by one of those boards.
> > >
> > > Hans, this means there are no more user of the soc_camera framework that I know
> > > of in Linux, and I guess we can now plan of to remove that framework.
> >
> > What's the status of this set? I think it'd be nice to get it in; the CEU
> > driver is the last using SoC camera framework.
> >
The series went in in the media tree in late June and I now see it in
v4.19-rc2.
Sorry for the confusion.
The other soc_camera series which is pending for approval is the one
removing dependencies on the framework from some SH defconfigs:
https://lkml.org/lkml/2018/7/4/323
Mauro was exitant to take this one through the media tree, and he's
probably right SH maintainers should at least ack the series. So far,
I haven't heard from them.
I'll try to rebase it on latest version and re-send.
Thanks
j
>
> There's an open comment from Geert on this series.
> I'll resend, then I guess it can be collected.
>
> > I guess an ack from the SH folks would be needed for these patches to go
> > through the media tree.
> >
>
> I would have loved to hear from them on this and other media patches
> which are sh-related. It hasn't happen, and as for the previous patches
> removing usage of the old ceu driver for SH boards, I guess this can go in
> through the media tree. But I let Hans decide how to handle this.
>
> > On the sensor driver patches --- please just move the files. The CEU was
> > the last that it was possible to use the drivers with.
> >
>
> My understanding was that Hans preferred to do it after all
> dependencies are moved away from soc_camera.
>
> Maybe at ELC-E we should have a status-check and decide how to move
> forward with soc_camera deprecation.
>
> Thanks
> j
>
> > --
> > Kind regards,
> >
> > Sakari Ailus
> > e-mail: sakari.ailus@iki.fi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-09-04 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 16:37 [PATCH 0/5] Remove sh_mobile_ceu_camera from arch/sh Jacopo Mondi
2018-05-28 16:37 ` [PATCH 1/5] media: i2c: Copy rj54n1cb0c soc_camera sensor driver Jacopo Mondi
2018-05-28 16:37 ` [PATCH 2/5] media: i2c: rj54n1: Remove soc_camera dependencies Jacopo Mondi
2018-05-28 16:37 ` [PATCH 3/5] arch: sh: kfr2r09: Use new renesas-ceu camera driver Jacopo Mondi
2018-05-29 7:33 ` Geert Uytterhoeven
2018-05-31 2:48 ` kbuild test robot
2018-05-28 16:37 ` [PATCH 4/5] arch: sh: ms7724se: " Jacopo Mondi
2018-05-28 16:37 ` [PATCH 5/5] arch: sh: ap325rxa: " Jacopo Mondi
2018-08-31 12:25 ` [PATCH 0/5] Remove sh_mobile_ceu_camera from arch/sh Sakari Ailus
2018-09-03 7:22 ` jacopo mondi
2018-09-04 9:33 ` jacopo mondi [this message]
2018-09-04 9:43 ` Sakari Ailus
2018-09-04 10:04 ` jacopo mondi
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=20180904093358.GK20333@w540 \
--to=jacopo@jmondi.org \
--cc=dalias@libc.org \
--cc=hverkuil@xs4all.nl \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=ysato@users.sourceforge.jp \
/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).