From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Cristina Ciocan <cristina.ciocan@intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Irina Tirdea <irina.tirdea@intel.com>,
Octavian Purdila <octavian.purdila@intel.com>
Subject: Re: [PATCH v3 1/6] pinctrl: baytrail: Add pin control data structures
Date: Fri, 1 Apr 2016 16:30:54 +0300 [thread overview]
Message-ID: <20160401133054.GS1719@lahna.fi.intel.com> (raw)
In-Reply-To: <CACRpkdZ0_qnm38xBRNQX-t9TbLgasoamOLraTLaTRk6amBUBhQ@mail.gmail.com>
On Fri, Apr 01, 2016 at 03:25:26PM +0200, Linus Walleij wrote:
> On Thu, Mar 31, 2016 at 10:04 AM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
>
> > My ack still applies to the whole series.
>
> I take it that I can just apply the v4 with your ACK on them.
That's right. Thanks!
next prev parent reply other threads:[~2016-04-01 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:05 [PATCH v3 0/6] Add pinctrl support for Baytrail Cristina Ciocan
2016-03-30 15:05 ` [PATCH v3 1/6] pinctrl: baytrail: Add pin control data structures Cristina Ciocan
2016-03-31 8:04 ` Mika Westerberg
2016-04-01 10:44 ` Cristina Ciocan
2016-04-01 13:25 ` Linus Walleij
2016-04-01 13:30 ` Mika Westerberg [this message]
2016-03-30 15:05 ` [PATCH v3 2/6] pinctrl: baytrail: Add pin control operations Cristina Ciocan
2016-03-30 15:05 ` [PATCH v3 3/6] pinctrl: baytrail: Update gpio chip operations Cristina Ciocan
2016-03-30 15:05 ` [PATCH v3 4/6] pinctrl: baytrail: Update irq " Cristina Ciocan
2016-03-30 15:05 ` [PATCH v3 5/6] pinctrl: baytrail: Register pin control handling Cristina Ciocan
2016-03-30 15:05 ` [PATCH v3 6/6] pinctrl: baytrail: Add debounce configuration Cristina Ciocan
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=20160401133054.GS1719@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=cristina.ciocan@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=irina.tirdea@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=octavian.purdila@intel.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