From: Hans de Goede <hdegoede@redhat.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Cox <alan@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org
Subject: [PATCH 4/7] staging: atomisp: Add INT0310 ACPI id to gc0310 driver
Date: Sun, 28 May 2017 14:31:50 +0200 [thread overview]
Message-ID: <20170528123153.18613-4-hdegoede@redhat.com> (raw)
In-Reply-To: <20170528123153.18613-1-hdegoede@redhat.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
drivers/staging/media/atomisp/i2c/gc0310.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/media/atomisp/i2c/gc0310.c b/drivers/staging/media/atomisp/i2c/gc0310.c
index 1ec616a15086..350fd7fd5b86 100644
--- a/drivers/staging/media/atomisp/i2c/gc0310.c
+++ b/drivers/staging/media/atomisp/i2c/gc0310.c
@@ -1455,6 +1455,7 @@ static int gc0310_probe(struct i2c_client *client,
static struct acpi_device_id gc0310_acpi_match[] = {
{"XXGC0310"},
+ {"INT0310"},
{},
};
--
2.13.0
next prev parent reply other threads:[~2017-05-28 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 12:31 [PATCH 1/7] staging: atomisp: Fix calling efivar_entry_get() with unaligned arguments Hans de Goede
2017-05-28 12:31 ` [PATCH 2/7] staging: atomisp: Do not call dev_warn with a NULL device Hans de Goede
2017-05-28 13:06 ` Andy Shevchenko
2017-05-28 12:31 ` [PATCH 3/7] staging: atomisp: Set step to 0 for mt9m114 menu control Hans de Goede
2017-05-28 12:31 ` Hans de Goede [this message]
2017-05-28 12:31 ` [PATCH 5/7] staging: atomisp: Add OVTI2680 ACPI id to ov2680 driver Hans de Goede
2017-05-28 12:31 ` [PATCH 6/7] staging: atomisp: Ignore errors from second gpio in " Hans de Goede
2017-05-28 12:31 ` [PATCH 7/7] staging: atomisp: Make ov2680 driver less chatty Hans de Goede
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=20170528123153.18613-4-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=alan@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox