Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Andrey Konovalov <andrey.konovalov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Revert "media: camss: Make use of V4L2_CAP_IO_MC"
Date: Tue, 29 Dec 2020 20:15:32 +0000	[thread overview]
Message-ID: <160927293294.13751.7996122840449983534.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201126150157.25870-1-andrey.konovalov@linaro.org>

Hello:

This series was applied to qcom/linux.git (refs/heads/for-next):

On Thu, 26 Nov 2020 18:01:56 +0300 you wrote:
> This reverts commit c90f1178dcac30dee5ddd29ec0513e7589aa866e.
> 
> The assumption of "Each entry in formats[] table has unique mbus_code"
> is valid for the RDI entities, but not for the PIX ones.
> 
> Reverting this patch and creating a new one which handles the PIX entities
> correctly results in smaller and more straightforward patch than doing the
> changes on top of the current version.
> 
> [...]

Here is the summary with links:
  - [v2,1/2] Revert "media: camss: Make use of V4L2_CAP_IO_MC"
    https://git.kernel.org/qcom/c/a3d412d4b9f3
  - [v2,2/2] media: camss: Make use of V4L2_CAP_IO_MC
    https://git.kernel.org/qcom/c/dfb5d3289716

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-12-29 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 15:01 [PATCH v2 1/2] Revert "media: camss: Make use of V4L2_CAP_IO_MC" Andrey Konovalov
2020-11-26 15:01 ` [PATCH v2 2/2] media: camss: Make use of V4L2_CAP_IO_MC Andrey Konovalov
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm [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=160927293294.13751.7996122840449983534.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=andrey.konovalov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.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