From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Lee Jones <lee@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mfd: intel-lpss: fix build error when !CONFIG_PM_SLEEP
Date: Mon, 05 Oct 2015 11:52:34 +0300 [thread overview]
Message-ID: <1444035154.8361.409.camel@linux.intel.com> (raw)
In-Reply-To: <20151005082800.GB3243@x1>
On Mon, 2015-10-05 at 09:28 +0100, Lee Jones wrote:
> >
> BTW: This patch has already been applied to my -fixes branch and will
> be sent to Mainline in a week or so.
Thanks!
P.S. I have got a message from kbuild bot that the bug is still there,
though I noticed that the patch made at least linux-next tree.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-10-05 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 13:06 [PATCH 1/1] mfd: intel-lpss: fix build error when !CONFIG_PM_SLEEP Andy Shevchenko
2015-10-01 14:45 ` Lee Jones
2015-10-02 12:21 ` Andy Shevchenko
2015-10-05 8:28 ` Lee Jones
2015-10-05 8:52 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-30 10:46 Andy Shevchenko
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=1444035154.8361.409.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.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