mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Perchanov <dmitry.perchanov@intel.com>
To: Sakari Ailus <sakari.ailus@intel.com>
Cc: linux-media@vger.kernel.org, mchehab@kernel.org,
	linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com,
	evgeni.raikhel@intel.com, demisrael@gmail.com
Subject: Re: [PATCH v3] media: uapi: v4l: Intel metadata format update
Date: Tue, 16 May 2023 11:11:49 +0300	[thread overview]
Message-ID: <1d425030407e11d776070e8ef12ce51dac3e0147.camel@intel.com> (raw)
In-Reply-To: <ZGIp7E94eAW7UFSP@valkosipuli.retiisi.eu>

On Mon, 2023-05-15 at 15:47 +0300, Sakari Ailus wrote:
> Hi Dmitry,
> 
> On Sun, May 14, 2023 at 12:36:50PM +0300, Dmitry Perchanov wrote:
> > Update metadata structure for Intel RealSense UVC/MIPI cameras.
> > Compliant to Intel Configuration version 3.
> > 
> > Signed-off-by: Dmitry Perchanov <dmitry.perchanov@intel.com>
> 
> Could you reply my comments on v2 and use my @intel.com address going
> forward?
It's done.
Thanks.
> 
> Thanks.
> 

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


  reply	other threads:[~2023-05-16  8:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14  9:36 Dmitry Perchanov
2023-05-15 12:47 ` Sakari Ailus
2023-05-16  8:11   ` Dmitry Perchanov [this message]
2023-06-01 16:08 ` [PATCH v4] " Dmitry Perchanov
2023-06-02 14:28   ` Sakari Ailus
2023-06-02 14:46   ` Laurent Pinchart
2023-06-02 15:00     ` Dmitry Perchanov
2023-06-02 15:25       ` Laurent Pinchart
2023-06-02 15:37         ` Dmitry Perchanov
2023-06-01 14:25 [PATCH v3] " Dmitry Perchanov

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=1d425030407e11d776070e8ef12ce51dac3e0147.camel@intel.com \
    --to=dmitry.perchanov@intel.com \
    --cc=demisrael@gmail.com \
    --cc=evgeni.raikhel@intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®