linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@codeaurora.org>
To: Stephen Boyd <sboyd@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pinctrl: qcom: add get_direction function
Date: Sat, 11 Feb 2017 15:32:15 -0600	[thread overview]
Message-ID: <51200db0-552b-221d-1e81-f1a3ee286c6c@codeaurora.org> (raw)
In-Reply-To: <8652c018-4051-5c77-3126-2d41d150518a@codeaurora.org>

Stephen Boyd wrote:
>> > +	/* 0 = output, 1 = input */
>> > +	return val & BIT(g->oe_bit) ? 0 : 1;
> Maybe we can use the macros GPIOF_DIR_IN and GPIOF_DIR_OUT here instead?

Ok, I posted a v2.

Is it too late for this patch to make the 4.11 merge window, or maybe 4.11-rc2? 
 From the perspective of our server platform, it's a bug fix.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.

  reply	other threads:[~2017-02-11 21:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 23:21 [PATCH] pinctrl: qcom: add get_direction function Timur Tabi
2017-02-10 23:25 ` Stephen Boyd
2017-02-11 21:32   ` Timur Tabi [this message]
2017-02-22 15:51     ` Linus Walleij
2017-02-22 15:49   ` Linus Walleij
2017-03-06 21:52     ` Timur Tabi
2017-03-14 21:41       ` Linus Walleij
2017-03-14 21:55         ` Timur Tabi
2017-03-14 23:30           ` Stephen Boyd
2017-03-14 23:34             ` Timur Tabi
2017-03-14 23:41               ` Stephen Boyd
2017-03-15  0:12                 ` Timur Tabi
2017-03-15  5:08                   ` Bjorn Andersson
2017-03-15 13:08                     ` Linus Walleij

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=51200db0-552b-221d-1e81-f1a3ee286c6c@codeaurora.org \
    --to=timur@codeaurora.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).