All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: "linux-media" <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [GIT PULL FOR v3.6] mostly remove V4L2_FL_LOCK_ALL_FOPS
Date: Thu, 5 Jul 2012 10:36:36 +0200	[thread overview]
Message-ID: <201207051036.36803.hverkuil@xs4all.nl> (raw)
In-Reply-To: <4FF55042.6090102@samsung.com>

On Thu 5 July 2012 10:28:50 Sylwester Nawrocki wrote:
> Hi Hans,
> 
> On 07/05/2012 08:54 AM, Hans Verkuil wrote:
> > Hi Sylwester,
> > 
> > It still doesn't apply. This patch starts with:
> > 
> > diff --git a/drivers/media/video/s5p-fimc/fimc-capture.c b/drivers/media/video/s5p-fimc/fimc-capture.c
> > index da2c40e..cb04a870 100644
> > --- a/drivers/media/video/s5p-fimc/fimc-capture.c
> > +++ b/drivers/media/video/s5p-fimc/fimc-capture.c
> > @@ -480,48 +480,59 @@ static int fimc_capture_set_default_format(struct fimc_dev *fimc);
> >  static int fimc_capture_open(struct file *file)
> >  {
> >         struct fimc_dev *fimc = video_drvdata(file);
> > -       int ret;
> > +       int ret = -EBUSY;
> > 
> > The actual current source code starts with:
> > 
> > static int fimc_capture_open(struct file *file)
> > {
> >         struct fimc_dev *fimc = video_drvdata(file);
> >         int ret = v4l2_fh_open(file);
> > 
> > Quite different. That 'int ret = v4l2_fh_open(file);' line was added June 10th, 2011, so
> > I don't understand why that isn't in your git repository.
> 
> Because is has been removed by one of patches from v4l-fimc-fixes branch
> that I sent to Mauro on 25th of May and is still not upstream.
> Branch v4l-fimc-next depends on v4l-fimc-fixes, sorry if it wasn't clear
> enough. You need to pull v4l-fimc-fixes branch first. If I would have
> rebased patches for -next then the fixup patches wouldn't apply. That
> just doesn't seem right.

Ah, OK. Sorry, I misunderstood.

In that case I'll just wait for Mauro to pull in the fimc-fixes, and then
I'll make another pull request to get this last FOPS usage fixed. If I start
pulling in fixes trees as well, then that's going to be confusing.

It's OK to have a second pull request later to finalize this as there is no
urgency associated with these patches.

Regards,

	Hans

> Mauro, are you going to send another pull request to Linus for 3.5-rc,
> including these patches: http://patchwork.linuxtv.org/patch/11503 ?
> 
> Regards,
> 

      reply	other threads:[~2012-07-05  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 17:42 [GIT PULL FOR v3.6] mostly remove V4L2_FL_LOCK_ALL_FOPS Hans Verkuil
2012-07-04 19:28 ` Sylwester Nawrocki
2012-07-05  6:54   ` Hans Verkuil
2012-07-05  8:28     ` Sylwester Nawrocki
2012-07-05  8:36       ` Hans Verkuil [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=201207051036.36803.hverkuil@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=s.nawrocki@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 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.