[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55E573AF.4060408@gmail.com>
Date: Tue, 1 Sep 2015 11:45:19 +0200
From: Matthias Brugger <matthias.bgg@...il.com>
To: Javier Martinez Canillas <javier@....samsung.com>,
linux-kernel@...r.kernel.org
Cc: Hongzhou Yang <hongzhou.yang@...iatek.com>,
Axel Lin <axel.lin@...ics.com>, Rob Herring <robh@...nel.org>,
linux-gpio@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Maoguang Meng <maoguang.meng@...iatek.com>,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
Yingjoe Chen <yingjoe.chen@...iatek.com>,
Colin Ian King <colin.king@...onical.com>
Subject: Re: [PATCH] pinctrl: mediatek: Consistently use the BIT() macro
On 29/08/15 01:25, Javier Martinez Canillas wrote:
> The mediatek pinctrl driver uses the BIT() macro instead of open
> coding 1 << n in all but one place. Replace this occurrence with
> the BIT() macro for consistency.
>
> Signed-off-by: Javier Martinez Canillas <javier@....samsung.com>
>
> ---
>
> drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/mediatek/pinctrl-mtk-common.c b/drivers/pinctrl/mediatek/pinctrl-mtk-common.c
> index 23f2de07f598..497b9125342a 100644
> --- a/drivers/pinctrl/mediatek/pinctrl-mtk-common.c
> +++ b/drivers/pinctrl/mediatek/pinctrl-mtk-common.c
> @@ -898,7 +898,7 @@ static int mtk_eint_flip_edge(struct mtk_pinctrl *pctl, int hwirq)
> int start_level, curr_level;
> unsigned int reg_offset;
> const struct mtk_eint_offsets *eint_offsets = &(pctl->devdata->eint_offsets);
> - u32 mask = 1 << (hwirq & 0x1f);
> + u32 mask = BIT(hwirq & 0x1f);
> u32 port = (hwirq >> 5) & eint_offsets->port_mask;
> void __iomem *reg = pctl->eint_reg_base + (port << 2);
> const struct mtk_desc_pin *pin;
>
Reviewed-by: Matthias Brugger <matthias.bgg@...il.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists