From: Loic Poulain <loic.poulain@intel.com>
To: "Westerberg, Mika" <mika.westerberg@intel.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Samuel Ortiz <samuel.ortiz@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] pinctrl: baytrail: Clear DIRECT_IRQ bit
Date: Wed, 24 Sep 2014 10:44:12 +0200 [thread overview]
Message-ID: <5422845C.1000909@intel.com> (raw)
In-Reply-To: <20140923183629.GU1786@lahna.fi.intel.com>
Yes I'm going to do a v3.
Regards,
Loic
On 23/09/2014 20:36, Westerberg, Mika wrote:
> On Tue, Sep 23, 2014 at 05:44:43PM +0200, Linus Walleij wrote:
>> On Wed, Sep 17, 2014 at 3:47 PM, Loic Poulain <loic.poulain@intel.com> wrote:
>>
>>> Direct Irq En bit can be initialized to a bad value.
>>> This bit has to be cleared for io access mode.
>>>
>>> Signed-off-by: Loic Poulain <loic.poulain@intel.com>
>>> ---
>>> v2: Apply over ff998356b644ebe723127bd9eec6040b59a4a4f6 + add Warning
>> I can't figure out if the maintainers like this patch or not.
>>
>> If you want it applied, please ACK it explicitly.
> I would like to get a bit better information in the changelog and the
> warning message should be more informative. I'll ACK it after that is
> done.
>
> Loic, are you going to do that?
--
Intel Open Source Technology Center
http://oss.intel.com/
prev parent reply other threads:[~2014-09-24 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 13:47 [PATCHv2] pinctrl: baytrail: Clear DIRECT_IRQ bit Loic Poulain
2014-09-18 7:49 ` Mika Westerberg
2014-09-18 9:31 ` Loic Poulain
2014-09-18 9:53 ` Mika Westerberg
2014-09-18 9:41 ` Samuel Ortiz
2014-09-18 9:55 ` Mika Westerberg
2014-09-18 23:59 ` eric ernst
2014-09-23 15:44 ` Linus Walleij
2014-09-23 18:36 ` Westerberg, Mika
2014-09-24 8:44 ` Loic Poulain [this message]
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=5422845C.1000909@intel.com \
--to=loic.poulain@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@intel.com \
--cc=samuel.ortiz@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 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.