All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xiang, Haihao" <haihao.xiang@intel.com>
To: "randy.li@rock-chips.com" <randy.li@rock-chips.com>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>
Cc: "alpha.lin@rock-chips.com" <alpha.lin@rock-chips.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-rockchip@lists.infradead.org"
	<linux-rockchip@lists.infradead.org>,
	"herman.chen@rock-chips.com" <herman.chen@rock-chips.com>,
	"eddie.cai@rock-chips.com" <eddie.cai@rock-chips.com>,
	"pawel@osciak.com" <pawel@osciak.com>,
	"libva@lists.freedesktop.org" <libva@lists.freedesktop.org>
Subject: Re: [Libva] something different ideas from chromium's decoder settings API
Date: Mon, 17 Oct 2016 04:42:52 +0000	[thread overview]
Message-ID: <1476679372.4871.40.camel@intel.com> (raw)
In-Reply-To: <91e1ac78-8a2f-35da-f84f-b35616153860@rock-chips.com>


Hi Randy, 

I saw a statement below at the end of your email:

======
This email message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
please
contact the sender by reply e-mail and destroy all copies of the
original
message. [Fuzhou Rockchip Electronics, INC. China mainland]
======

Please do not send your email to libva@lists.freedesktop.org if you
don't want to discuss your question/idea publicly because libva@lists.f
reedesktop is only used for public discussion of libva, otherwise
please remove the above statement in your email.

Thanks
Haihao


      reply	other threads:[~2016-10-17  4:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17  4:02 something different ideas from chromium's decoder settings API Randy Li
2016-10-17  4:42 ` Xiang, Haihao [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=1476679372.4871.40.camel@intel.com \
    --to=haihao.xiang@intel.com \
    --cc=alpha.lin@rock-chips.com \
    --cc=eddie.cai@rock-chips.com \
    --cc=herman.chen@rock-chips.com \
    --cc=hverkuil@xs4all.nl \
    --cc=libva@lists.freedesktop.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pawel@osciak.com \
    --cc=randy.li@rock-chips.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.