Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/793174/?format=api
{ "id": 793174, "url": "http://patchwork.ozlabs.org/api/patches/793174/?format=api", "web_url": "http://patchwork.ozlabs.org/project/linux-i2c/patch/1500954024-6860-3-git-send-email-preid@electromag.com.au/", "project": { "id": 35, "url": "http://patchwork.ozlabs.org/api/projects/35/?format=api", "name": "Linux I2C development", "link_name": "linux-i2c", "list_id": "linux-i2c.vger.kernel.org", "list_email": "linux-i2c@vger.kernel.org", "web_url": "", "scm_url": "", "webscm_url": "", "list_archive_url": "", "list_archive_url_format": "", "commit_url_format": "" }, "msgid": "<1500954024-6860-3-git-send-email-preid@electromag.com.au>", "list_archive_url": null, "date": "2017-07-25T03:40:16", "name": "[v10,02/10] i2c: i2c-smbus: Move i2c_setup_smbus_alert from i2c-smbus to i2c-core-smbus", "commit_ref": null, "pull_url": null, "state": "superseded", "archived": false, "hash": "d64d199301ba2e7162a27b1faff99e4653712dc3", "submitter": { "id": 66145, "url": "http://patchwork.ozlabs.org/api/people/66145/?format=api", "name": "Phil Reid", "email": "preid@electromag.com.au" }, "delegate": null, "mbox": "http://patchwork.ozlabs.org/project/linux-i2c/patch/1500954024-6860-3-git-send-email-preid@electromag.com.au/mbox/", "series": [], "comments": "http://patchwork.ozlabs.org/api/patches/793174/comments/", "check": "pending", "checks": "http://patchwork.ozlabs.org/api/patches/793174/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<linux-i2c-owner@vger.kernel.org>", "X-Original-To": "incoming@patchwork.ozlabs.org", "Delivered-To": "patchwork-incoming@bilbo.ozlabs.org", "Authentication-Results": "ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-i2c-owner@vger.kernel.org;\n\treceiver=<UNKNOWN>)", "Received": [ "from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xGkY31LfZz9s8J\n\tfor <incoming@patchwork.ozlabs.org>;\n\tTue, 25 Jul 2017 13:40:55 +1000 (AEST)", "(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1754146AbdGYDkr (ORCPT <rfc822;incoming@patchwork.ozlabs.org>);\n\tMon, 24 Jul 2017 23:40:47 -0400", "from anchovy3.45ru.net.au ([203.30.46.155]:36141 \"EHLO\n\tanchovy.45ru.net.au\" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org\n\twith ESMTP id S1754588AbdGYDkg (ORCPT\n\t<rfc822; linux-i2c@vger.kernel.org>); Mon, 24 Jul 2017 23:40:36 -0400", "(qmail 14937 invoked by uid 5089); 25 Jul 2017 03:40:33 -0000", "by simscan 1.2.0 ppid: 14859, pid: 14860, t: 0.0919s\n\tscanners: regex: 1.2.0 attach: 1.2.0 clamav: 0.88.3/m:40/d:1950", "from unknown (HELO preid-centos7.electromag.com.au)\n\t(preid@electromag.com.au@203.59.230.133)\n\tby anchovy2.45ru.net.au with ESMTPA; 25 Jul 2017 03:40:32 -0000", "by preid-centos7.electromag.com.au (Postfix, from userid 1000)\n\tid 80059302644C2; Tue, 25 Jul 2017 11:40:29 +0800 (AWST)" ], "X-RBL": "$rbltext", "From": "Phil Reid <preid@electromag.com.au>", "To": "wsa@the-dreams.de, robh+dt@kernel.org, mark.rutland@arm.com,\n\tsre@kernel.org, jdelvare@suse.com, jglauber@cavium.com,\n\tdavid.daney@cavium.com, peda@axentia.se, preid@electromag.com.au,\n\tbenjamin.tissoires@redhat.com, linux-i2c@vger.kernel.org,\n\tdevicetree@vger.kernel.org, linux-pm@vger.kernel.org", "Subject": "[PATCH v10 02/10] i2c: i2c-smbus: Move i2c_setup_smbus_alert from\n\ti2c-smbus to i2c-core-smbus", "Date": "Tue, 25 Jul 2017 11:40:16 +0800", "Message-Id": "<1500954024-6860-3-git-send-email-preid@electromag.com.au>", "X-Mailer": "git-send-email 1.8.3.1", "In-Reply-To": "<1500954024-6860-1-git-send-email-preid@electromag.com.au>", "References": "<1500954024-6860-1-git-send-email-preid@electromag.com.au>", "Sender": "linux-i2c-owner@vger.kernel.org", "Precedence": "bulk", "List-ID": "<linux-i2c.vger.kernel.org>", "X-Mailing-List": "linux-i2c@vger.kernel.org" }, "content": "In preparation to adding of_i2c_setup_smbus_alert() move\ni2c_setup_smbus_alert() to core module. of_i2c_setup_smbus_alert()\nwill call i2c_setup_smbus_alert() and this avoid module dependecy issues.\n\nSigned-off-by: Phil Reid <preid@electromag.com.au>\n---\n drivers/i2c/i2c-core-smbus.c | 33 +++++++++++++++++++++++++++++++++\n drivers/i2c/i2c-smbus.c | 32 --------------------------------\n 2 files changed, 33 insertions(+), 32 deletions(-)", "diff": "diff --git a/drivers/i2c/i2c-core-smbus.c b/drivers/i2c/i2c-core-smbus.c\nindex 10f00a8..7f3ec02 100644\n--- a/drivers/i2c/i2c-core-smbus.c\n+++ b/drivers/i2c/i2c-core-smbus.c\n@@ -17,6 +17,7 @@\n #include <linux/device.h>\n #include <linux/err.h>\n #include <linux/i2c.h>\n+#include <linux/i2c-smbus.h>\n \n #define CREATE_TRACE_POINTS\n #include <trace/events/smbus.h>\n@@ -592,3 +593,35 @@ s32 i2c_smbus_read_i2c_block_data_or_emulated(const struct i2c_client *client,\n \treturn i;\n }\n EXPORT_SYMBOL(i2c_smbus_read_i2c_block_data_or_emulated);\n+\n+/**\n+ * i2c_setup_smbus_alert - Setup SMBus alert support\n+ * @adapter: the target adapter\n+ * @setup: setup data for the SMBus alert handler\n+ * Context: can sleep\n+ *\n+ * Setup handling of the SMBus alert protocol on a given I2C bus segment.\n+ *\n+ * Handling can be done either through our IRQ handler, or by the\n+ * adapter (from its handler, periodic polling, or whatever).\n+ *\n+ * NOTE that if we manage the IRQ, we *MUST* know if it's level or\n+ * edge triggered in order to hand it to the workqueue correctly.\n+ * If triggering the alert seems to wedge the system, you probably\n+ * should have said it's level triggered.\n+ *\n+ * This returns the ara client, which should be saved for later use with\n+ * i2c_handle_smbus_alert() and ultimately i2c_unregister_device(); or NULL\n+ * to indicate an error.\n+ */\n+struct i2c_client *i2c_setup_smbus_alert(struct i2c_adapter *adapter,\n+\t\t\t\t\t struct i2c_smbus_alert_setup *setup)\n+{\n+\tstruct i2c_board_info ara_board_info = {\n+\t\tI2C_BOARD_INFO(\"smbus_alert\", 0x0c),\n+\t\t.platform_data = setup,\n+\t};\n+\n+\treturn i2c_new_device(adapter, &ara_board_info);\n+}\n+EXPORT_SYMBOL_GPL(i2c_setup_smbus_alert);\ndiff --git a/drivers/i2c/i2c-smbus.c b/drivers/i2c/i2c-smbus.c\nindex d4af270..d0bb035 100644\n--- a/drivers/i2c/i2c-smbus.c\n+++ b/drivers/i2c/i2c-smbus.c\n@@ -183,38 +183,6 @@ static int smbalert_remove(struct i2c_client *ara)\n };\n \n /**\n- * i2c_setup_smbus_alert - Setup SMBus alert support\n- * @adapter: the target adapter\n- * @setup: setup data for the SMBus alert handler\n- * Context: can sleep\n- *\n- * Setup handling of the SMBus alert protocol on a given I2C bus segment.\n- *\n- * Handling can be done either through our IRQ handler, or by the\n- * adapter (from its handler, periodic polling, or whatever).\n- *\n- * NOTE that if we manage the IRQ, we *MUST* know if it's level or\n- * edge triggered in order to hand it to the workqueue correctly.\n- * If triggering the alert seems to wedge the system, you probably\n- * should have said it's level triggered.\n- *\n- * This returns the ara client, which should be saved for later use with\n- * i2c_handle_smbus_alert() and ultimately i2c_unregister_device(); or NULL\n- * to indicate an error.\n- */\n-struct i2c_client *i2c_setup_smbus_alert(struct i2c_adapter *adapter,\n-\t\t\t\t\t struct i2c_smbus_alert_setup *setup)\n-{\n-\tstruct i2c_board_info ara_board_info = {\n-\t\tI2C_BOARD_INFO(\"smbus_alert\", 0x0c),\n-\t\t.platform_data = setup,\n-\t};\n-\n-\treturn i2c_new_device(adapter, &ara_board_info);\n-}\n-EXPORT_SYMBOL_GPL(i2c_setup_smbus_alert);\n-\n-/**\n * i2c_handle_smbus_alert - Handle an SMBus alert\n * @ara: the ARA client on the relevant adapter\n * Context: can't sleep\n", "prefixes": [ "v10", "02/10" ] }