All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Raikhel, Evgeni" <evgeni.raikhel@intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: RE: [PATCH] UVC Module  - Support Intel RealSense SR300 Depth Camera formats
Date: Mon, 5 Dec 2016 13:34:58 +0000	[thread overview]
Message-ID: <AA09C8071EEEFC44A7852ADCECA86673A1EABA@hasmsx108.ger.corp.intel.com> (raw)
In-Reply-To: <19511557.1CIWCiALqy@avalon>

Hi Laurent,

Thanks for the feedback - I resubmitted the patches inline, as requested.

Regards,
Evgeni Raikhel

-----Original Message-----
From: Laurent Pinchart [mailto:laurent.pinchart@ideasonboard.com] 
Sent: Monday, December 05, 2016 13:02
To: Raikhel, Evgeni <evgeni.raikhel@intel.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] UVC Module - Support Intel RealSense SR300 Depth Camera formats

Hi Evgeni,

Thank you for the patch.

On Monday 05 Dec 2016 10:06:55 Raikhel, Evgeni wrote:
> Specify GUID and FourCC codes mapping for Depth-related pixel formats 
> advertised by Intel RealSense(tm) SR300 depth camera. Provide 
> documentation for the new INZI pixel format introduced.

Could you please resend the patches inline instead of as attachments ? See Documentation/SubmittingPatches for more information.

--
Regards,

Laurent Pinchart

---------------------------------------------------------------------
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:[~2016-12-05 13:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 10:06 [PATCH] UVC Module - Support Intel RealSense SR300 Depth Camera formats Raikhel, Evgeni
2016-12-05 11:01 ` Laurent Pinchart
2016-12-05 13:34   ` Raikhel, Evgeni [this message]
2017-02-08  8:34 ` [PATCH v2 1/2] Documentation: Intel SR300 Depth camera INZI format evgeni.raikhel
2017-02-08  8:34   ` [PATCH v2 2/2] uvcvideo: Add support for Intel SR300 depth camera evgeni.raikhel
2017-02-08 13:41     ` Laurent Pinchart
2017-02-08 13:39   ` [PATCH v2 1/2] Documentation: Intel SR300 Depth camera INZI format Laurent Pinchart
2017-02-19 16:05 ` [PATCH v3 0/2] Intel SR300 Depth Formats evgeni.raikhel
2017-02-19 16:14 ` [PATCH v3 0/2] Intel Depth Formats for SR300 camera evgeni.raikhel
2017-02-19 16:14   ` [PATCH v3 1/2] Documentation: Intel SR300 Depth camera INZI format evgeni.raikhel
2017-02-19 16:45     ` Laurent Pinchart
2017-02-19 16:14   ` [PATCH v3 2/2] uvcvideo: Add support for Intel SR300 depth camera evgeni.raikhel
2017-03-02 23:43 ` [PATCH v4 0/2] Intel Depth Formats for SR300 Camera evgeni.raikhel
2017-03-02 23:43   ` [PATCH v4 1/2] Documentation: Intel SR300 Depth camera INZI format evgeni.raikhel
2017-04-03  8:58     ` Hans Verkuil
2017-03-02 23:43   ` [PATCH v4 2/2] uvcvideo: Add support for Intel SR300 depth camera evgeni.raikhel
2017-04-03  8:53   ` [PATCH v4 0/2] Intel Depth Formats for SR300 Camera Raikhel, Evgeni
2017-04-04 10:35     ` Laurent Pinchart

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=AA09C8071EEEFC44A7852ADCECA86673A1EABA@hasmsx108.ger.corp.intel.com \
    --to=evgeni.raikhel@intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@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 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.