All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Sylwester Nawrocki <snjw23@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH FOR 3.3] VIDIOC_LOG_STATUS support for sub-devices
Date: Fri, 06 Jan 2012 12:38:22 -0200	[thread overview]
Message-ID: <4F07075E.8050301@redhat.com> (raw)
In-Reply-To: <4EFEEEB7.2020109@gmail.com>

On 31-12-2011 09:15, Sylwester Nawrocki wrote:
> Hi Mauro,
> 
> The following changes since commit 3220eb73c5647af4c1f18e32c12dccb8adbac59d:
> 
>   s5p-fimc: Add support for alpha component configuration (2011-12-20 19:46:55
> +0100)
> 
> are available in the git repository at:
>   git://git.infradead.org/users/kmpark/linux-samsung v4l_mbus
> 
> This one patch enables VIDIOC_LOG_STATUS on subdev nodes.
> 
> Sylwester Nawrocki (1):
>       v4l: Add VIDIOC_LOG_STATUS support for sub-device nodes


Weird... when trying to pull from your tree, several other patches appeared.
After removing the ones that seemed to be already applied, there are still
those that seemed to still apply:

Nov,17 2011: s5p-fimc: Prevent lock up caused by incomplete H/W initialization
Oct, 1 2011: v4l: Add VIDIOC_LOG_STATUS support for sub-device nodes
Dec, 9 2011: v4l: Add new framesamples field to struct v4l2_mbus_framefmt
Dec,15 2011: v4l: Update subdev drivers to handle framesamples parameter
Dec,12 2011: m5mols: Add buffer size configuration support for compressed streams
Nov,21 2011: s5p-fimc: Add media bus framesamples support

Could you please double-check and, if possible, rebase your tree, to avoid
the risk of applying something that is not ok yet, nor to miss something?

Thanks!
Mauro

  reply	other threads:[~2012-01-06 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 11:15 [PATCH FOR 3.3] VIDIOC_LOG_STATUS support for sub-devices Sylwester Nawrocki
2012-01-06 14:38 ` Mauro Carvalho Chehab [this message]
2012-01-06 14:55   ` Sylwester Nawrocki

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=4F07075E.8050301@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=snjw23@gmail.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.