From: Chanwoo Choi <cw00.choi@samsung.com>
To: tomasz.figa@gmail.com, krzk@kernel.org, s.nawrocki@samsung.com,
linus.walleij@linaro.org, kgene@kernel.org
Cc: javier@osg.samsung.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>
Subject: [PATCH 0/2] pinctrl: samsung: Fix PINCFG_TYPE_DRV bitfields for Exynos5433
Date: Wed, 22 Mar 2017 17:03:30 +0900 [thread overview]
Message-ID: <1490169812-25225-1-git-send-email-cw00.choi@samsung.com> (raw)
In-Reply-To: CGME20170322080334epcas1p2531fbfdd3c3e033b0f67c5a5cf63b6a1@epcas1p2.samsung.com
This patches add the missing part about PINCFG_TYPE_DRV bitfields
for Exynos5433 when merged the multiple patches for pinctrl-exynos.c
and this patch removes the unused EXYNOS_PIN_BANK_EINTW_EXT macro.
Also, patch1 and patch2 will be possible squashed if the separate patch
is not necesasry.
Chanwoo Choi (2):
pinctrl: samsung: Add missing part for PINCFG_TYPE_DRV of Exynos5433
pinctrl: samsung: Remove unused pin-bank macro
drivers/pinctrl/samsung/pinctrl-exynos.c | 80 ++++++++++++++++----------------
drivers/pinctrl/samsung/pinctrl-exynos.h | 11 -----
2 files changed, 40 insertions(+), 51 deletions(-)
--
1.9.1
next parent reply other threads:[~2017-03-22 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170322080334epcas1p2531fbfdd3c3e033b0f67c5a5cf63b6a1@epcas1p2.samsung.com>
2017-03-22 8:03 ` Chanwoo Choi [this message]
[not found] ` <CGME20170322080335epcas5p2c169c15e1b9db200aee9ca83c71699f6@epcas5p2.samsung.com>
2017-03-22 8:03 ` [PATCH 1/2] pinctrl: samsung: Add missing part for PINCFG_TYPE_DRV of Exynos5433 Chanwoo Choi
2017-03-22 18:00 ` Krzysztof Kozlowski
[not found] ` <CGME20170322080335epcas5p2f514974da14bd739d712cf1ab1a4cc0c@epcas5p2.samsung.com>
2017-03-22 8:03 ` [PATCH 2/2] pinctrl: samsung: Remove unused pin-bank macro Chanwoo Choi
2017-03-22 18:11 ` Krzysztof Kozlowski
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=1490169812-25225-1-git-send-email-cw00.choi@samsung.com \
--to=cw00.choi@samsung.com \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--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-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tomasz.figa@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;
as well as URLs for NNTP newsgroup(s).