linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jacopo mondi <jacopo@jmondi.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "Hans Verkuil" <hverkuil@xs4all.nl>,
	"Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
	"Ezequiel Garcia" <ezequiel@collabora.com>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	ysato@users.sourceforge.jp, dalias@libc.org,
	linux-sh@vger.kernel.org
Subject: Re: [GIT PULL FOR v4.19] Various fixes
Date: Wed, 25 Jul 2018 07:18:53 +0000	[thread overview]
Message-ID: <20180725071853.GN6784@w540> (raw)
In-Reply-To: <20180724190413.77025078@coco.lan>

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

Hi Mauro,
   I understand, and I failed to cc the SH people initially.

Roping in Sato-san, Rich and the SH list.
Could you guys please have a look here? I've gone through the media
tree as all these changes sparkled from soc_camera removal, and while
I was there I updated the defconfigs before enabling CEU and disabling
soc_camera.

How long before we miss v4.19 Mauro?

Thanks
   j

On Tue, Jul 24, 2018 at 07:04:13PM -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 18 Jul 2018 12:38:58 +0200
> Hans Verkuil <hverkuil@xs4all.nl> escreveu:
>
> > Hi Mauro,
> >
> > Various fixes. Please note that I re-added the 'Add support for STD ioctls on subdev nodes'
> > patch. It really is needed.
> >
> > Regards,
> >
> > 	Hans
> >
>
> > Jacopo Mondi (9):
> >       sh: defconfig: migor: Update defconfig
> >       sh: defconfig: migor: Enable CEU and sensor drivers
> >       sh: defconfig: ecovec: Update defconfig
> >       sh: defconfig: ecovec: Enable CEU and video drivers
> >       sh: defconfig: se7724: Update defconfig
> >       sh: defconfig: se7724: Enable CEU and sensor driver
> >       sh: defconfig: ap325rxa: Update defconfig
> >       sh: defconfig: ap325rxa: Enable CEU and sensor driver
>
> I didn't apply the above ones. I understand you want to enable
> the sensor drivers there, but It should either go via SUPERH
> tree or we would need his ack to merge on our tree.
>
> >       sh: migor: Remove stale soc_camera include
>
> It caused me lots of doubts if we should either apply this one
> via the media tree or not. I ended by applying, as we're maintaining
> the soc_camera stuff, with are being removed. So, it makes more sense
> to merge it via our tree.
>
> Still, it would be nicer if we had the SUPERH maintainer's ack on
> it.
>
>
> Thanks,
> Mauro

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

       reply	other threads:[~2018-07-25  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a9296b29-09ad-9379-0786-de282b71abf2@xs4all.nl>
     [not found] ` <20180724190413.77025078@coco.lan>
2018-07-25  7:18   ` jacopo mondi [this message]
2018-07-25  9:54     ` [GIT PULL FOR v4.19] Various fixes Mauro Carvalho Chehab

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=20180725071853.GN6784@w540 \
    --to=jacopo@jmondi.org \
    --cc=dalias@libc.org \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo+renesas@jmondi.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --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).