From: Hans de Goede <hdegoede@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Robert Butora <robert.butora.fi@gmail.com>
Subject: [GIT PULL patches for 3.16] media:gspca:dtcs033 Clean sparse check warnings on endianess
Date: Fri, 18 Apr 2014 11:59:46 +0200 [thread overview]
Message-ID: <5350F792.4010903@redhat.com> (raw)
Hi Mauro,
Please pull from my gspca git tree for a gspca fix for some sparse errors.
The following changes since commit 701b57ee3387b8e3749845b02310b5625fbd8da0:
[media] vb2: Add videobuf2-dvb support (2014-04-16 18:59:29 -0300)
are available in the git repository at:
git://linuxtv.org/hgoede/gspca.git media-for_v3.16
for you to fetch changes up to f1262be04ca6bfc57d13b21b247c3d9f6818caff:
media:gspca:dtcs033 Clean sparse check warnings on endianess (2014-04-18 11:31:50 +0200)
----------------------------------------------------------------
Robert Butora (1):
media:gspca:dtcs033 Clean sparse check warnings on endianess
drivers/media/usb/gspca/dtcs033.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
Thanks & Regards,
Hans
reply other threads:[~2014-04-18 9:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5350F792.4010903@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=robert.butora.fi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox