From: Hanna Hawa <hhhawa@amazon.com> To: <tony@atomide.com>, <haojian.zhuang@linaro.org>, <linus.walleij@linaro.org> Cc: <dwmw@amazon.co.uk>, <benh@amazon.com>, <ronenk@amazon.com>, <talel@amazon.com>, <jonnyc@amazon.com>, <hanochu@amazon.com>, <tgershi@amazon.com>, <linux-arm-kernel@lists.infradead.org>, <linux-omap@vger.kernel.org>, <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <hhhawa@amazon.com> Subject: [PATCH v2 0/3] Fix pinctrl-single pcs_pin_dbg_show() Date: Tue, 16 Mar 2021 22:24:31 +0200 [thread overview] Message-ID: <20210316202434.27555-1-hhhawa@amazon.com> (raw) These patches fix the pcs_pin_dbg_show() function for the scenario where a single register controls multiple pins (i.e. bits_per_mux != 0). Additionally, the common formula is moved to a separate function to allow reuse. Changes since v1: ----------------- - remove unused variable in In function 'pcs_allocate_pin_table' (Reported-by: kernel test robot <lkp@intel.com>) Hanna Hawa (3): pinctrl: pinctrl-single: remove unused variable pinctrl: pinctrl-single: remove unused parameter pinctrl: pinctrl-single: fix pcs_pin_dbg_show() when bits_per_mux != 0 drivers/pinctrl/pinctrl-single.c | 76 ++++++++++++++++++++------------ 1 file changed, 47 insertions(+), 29 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Hanna Hawa <hhhawa@amazon.com> To: <tony@atomide.com>, <haojian.zhuang@linaro.org>, <linus.walleij@linaro.org> Cc: <dwmw@amazon.co.uk>, <benh@amazon.com>, <ronenk@amazon.com>, <talel@amazon.com>, <jonnyc@amazon.com>, <hanochu@amazon.com>, <tgershi@amazon.com>, <linux-arm-kernel@lists.infradead.org>, <linux-omap@vger.kernel.org>, <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <hhhawa@amazon.com> Subject: [PATCH v2 0/3] Fix pinctrl-single pcs_pin_dbg_show() Date: Tue, 16 Mar 2021 22:24:31 +0200 [thread overview] Message-ID: <20210316202434.27555-1-hhhawa@amazon.com> (raw) These patches fix the pcs_pin_dbg_show() function for the scenario where a single register controls multiple pins (i.e. bits_per_mux != 0). Additionally, the common formula is moved to a separate function to allow reuse. Changes since v1: ----------------- - remove unused variable in In function 'pcs_allocate_pin_table' (Reported-by: kernel test robot <lkp@intel.com>) Hanna Hawa (3): pinctrl: pinctrl-single: remove unused variable pinctrl: pinctrl-single: remove unused parameter pinctrl: pinctrl-single: fix pcs_pin_dbg_show() when bits_per_mux != 0 drivers/pinctrl/pinctrl-single.c | 76 ++++++++++++++++++++------------ 1 file changed, 47 insertions(+), 29 deletions(-) -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-03-16 20:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-16 20:24 Hanna Hawa [this message] 2021-03-16 20:24 ` [PATCH v2 0/3] Fix pinctrl-single pcs_pin_dbg_show() Hanna Hawa 2021-03-16 20:24 ` [PATCH v2 1/3] pinctrl: pinctrl-single: remove unused variable Hanna Hawa 2021-03-16 20:24 ` Hanna Hawa 2021-03-16 20:24 ` [PATCH v2 2/3] pinctrl: pinctrl-single: remove unused parameter Hanna Hawa 2021-03-16 20:24 ` Hanna Hawa 2021-03-16 20:24 ` [PATCH v2 3/3] pinctrl: pinctrl-single: fix pcs_pin_dbg_show() when bits_per_mux != 0 Hanna Hawa 2021-03-16 20:24 ` Hanna Hawa 2021-03-17 12:27 ` Andy Shevchenko 2021-03-17 12:27 ` Andy Shevchenko 2021-03-17 19:35 ` Hawa, Hanna 2021-03-17 19:35 ` Hawa, Hanna 2021-03-17 21:41 [PATCH v2 0/3] Fix pinctrl-single pcs_pin_dbg_show() Hanna Hawa 2021-03-17 21:41 ` Hanna Hawa
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=20210316202434.27555-1-hhhawa@amazon.com \ --to=hhhawa@amazon.com \ --cc=benh@amazon.com \ --cc=dwmw@amazon.co.uk \ --cc=hanochu@amazon.com \ --cc=haojian.zhuang@linaro.org \ --cc=jonnyc@amazon.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=ronenk@amazon.com \ --cc=talel@amazon.com \ --cc=tgershi@amazon.com \ --cc=tony@atomide.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: linkBe 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.