public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [GIT PULL for v4.5-rc1] media controller next gen patch series
Date: Thu, 21 Jan 2016 14:31:50 +0530	[thread overview]
Message-ID: <20160121090150.GB10063@sudip-pc> (raw)
In-Reply-To: <569E3FC1.5060306@osg.samsung.com>

On Tue, Jan 19, 2016 at 10:53:05AM -0300, Javier Martinez Canillas wrote:
> Hello,
> 
> On 01/19/2016 07:20 AM, Mauro Carvalho Chehab wrote:
> >Em Tue, 19 Jan 2016 11:02:30 +0100
> >Geert Uytterhoeven <geert@linux-m68k.org> escreveu:
> >
> >>Hi Mauro,
> >>
> >>On Tue, Jan 12, 2016 at 11:43 AM, Mauro Carvalho Chehab
> >><mchehab@osg.samsung.com> wrote:
> >>>That's the second part of the media patches. It contains the media controller
> >>>next generation patches, with is the result of one year of discussions and
> >>>development. It also contains patches to enable media controller support
> >>>at the DVB subsystem.
> >>>
> >>>The goal is to improve the media controller to allow proper support for
> >>>other types of Video4Linux devices (radio and TV ones) and to extend the
> >>>media controller functionality to allow it to be used by other subsystems
> >>>like DVB, ALSA and IIO.
> >>>
> >>>In order to use the new functionality, a new ioctl is needed
> >>>(MEDIA_IOC_G_TOPOLOGY). As we're still discussing how to pack the struct
> >>>fields of this ioctl in order to avoid compat32 issues, I decided to add
> >>>a patch at the end of this series commenting out the new ioctl, in order
> >>>to postpone the addition of the new ioctl to the next Kernel version (4.6).
> >>>With that, no userspace visible changes should happen at the media
> >>>controller API, as the existing ioctls are untouched. Yet, it helps
> >>>DVB, ALSA and IIO developers to develop and test the patches adding media
> >>>controller support there, as the core will contain all required internal
> >>>changes to allow adding support for devices that belong to those
> >>>subsystems.
> >>>
> >>>Regards,
> >>>Mauro
> >>>
> >>>The following changes since commit 768acf46e1320d6c41ed1b7c4952bab41c1cde79:
> >>>
> >>>   [media] rc: sunxi-cir: Initialize the spinlock properly (2015-12-23 15:51:40 -0200)
> >>>
> >>>are available in the git repository at:
> >>>
> >>>   git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v4.5-2
> >>>
> >>>for you to fetch changes up to be0270ec89e6b9b49de7e533dd1f3a89ad34d205:
> >>>
> >>>   [media] Postpone the addition of MEDIA_IOC_G_TOPOLOGY (2016-01-11 12:35:17 -0200)
> >>
> >>After merging this into mainline, I get the BUG_ON() and crash I reported ca.
> >>one month ago in "vsp1 BUG_ON() and crash (Re: [PATCH v9 03/12] media:
> >>Entities, pads and links)" ( https://lkml.org/lkml/2015/12/14/373).
> >
> >Not sure what happened here, as this was supposed to have fixed already.
> >I'll ask Javier to take a look into it and work with you for us to get it
> >fixed ASAP.
> >
> 
> There was a bug in my patch that split the entities registration and links
> creation. I posted a fix that was already been tested by Geert:
> 
> https://patchwork.linuxtv.org/patch/32675/

I will also request you to have a look at
https://patchwork.linuxtv.org/patch/32425/

without it m32r allmodconfig will be broken for rc1.

regards
sudip

      reply	other threads:[~2016-01-21  9:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 10:43 [GIT PULL for v4.5-rc1] media controller next gen patch series Mauro Carvalho Chehab
2016-01-12 20:54 ` Stephen Rothwell
2016-01-12 20:58   ` Linus Torvalds
2016-01-12 21:07     ` Stephen Rothwell
2016-01-13  1:36       ` Mauro Carvalho Chehab
2016-01-12 22:29 ` Laurent Pinchart
2016-01-13  2:46   ` Mauro Carvalho Chehab
2016-01-19 10:02 ` Geert Uytterhoeven
2016-01-19 10:20   ` Mauro Carvalho Chehab
2016-01-19 13:53     ` Javier Martinez Canillas
2016-01-21  9:01       ` Sudip Mukherjee [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=20160121090150.GB10063@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=javier@osg.samsung.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=torvalds@linux-foundation.org \
    /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