From: Dan Carpenter <dan.carpenter@oracle.com>
To: Volokh Konstantin <volokh84@gmail.com>
Cc: linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
mchehab@redhat.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, dhowells@redhat.com,
rdunlap@xenotime.net, hans.verkuil@cisco.com,
justinmattock@gmail.com
Subject: Re: [PATCH 3/4] staging: media: go7007: i2c GPIO initialization Reset i2c stuff for GO7007_BOARDID_ADLINK_MPG24 need reset GPIO always when encoder initialize
Date: Wed, 16 Jan 2013 16:36:08 +0300 [thread overview]
Message-ID: <20130116133608.GH4584@mwanda> (raw)
In-Reply-To: <1358341251-10087-3-git-send-email-volokh84@gmail.com>
You've added the writes for GO7007_BOARDID_ADLINK_MPG24 but removed
them for GO7007_BOARDID_XMEN and GO7007_BOARDID_XMEN_III. Won't
that break those boards?
regards,
dan carpenter
next prev parent reply other threads:[~2013-01-16 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:00 [PATCH 1/4] staging: media: go7007: memory clear fix memory clearing for v4l2_subdev allocation Volokh Konstantin
2013-01-16 13:00 ` [PATCH 2/4] staging: media: go7007: firmware protection Protection for unfirmware load Volokh Konstantin
2013-01-16 13:35 ` Dan Carpenter
2013-01-16 13:42 ` Volokh Konstantin
2013-01-16 18:03 ` Ezequiel Garcia
2013-01-16 13:00 ` [PATCH 3/4] staging: media: go7007: i2c GPIO initialization Reset i2c stuff for GO7007_BOARDID_ADLINK_MPG24 need reset GPIO always when encoder initialize Volokh Konstantin
2013-01-16 13:36 ` Dan Carpenter [this message]
2013-01-16 14:00 ` Volokh Konstantin
2013-01-16 14:33 ` Dan Carpenter
2013-01-16 13:00 ` [PATCH 4/4] staging: media: go7007: call_all stream stuff Some Additional stuff for v4l2_subdev stream events partial need for new style framework. Also need for wis_tw2804 notification stuff Volokh Konstantin
2013-01-16 13:20 ` [PATCH 1/4] staging: media: go7007: memory clear fix memory clearing for v4l2_subdev allocation Dan Carpenter
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=20130116133608.GH4584@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=volokh84@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 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.