public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: linus.walleij@linaro.org, bgolaszewski@baylibre.com,
	rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] gpio: merrifield: Fix build err without CONFIG_ACPI
Date: Fri, 5 Apr 2019 13:07:03 +0300	[thread overview]
Message-ID: <20190405100703.GX9224@smile.fi.intel.com> (raw)
In-Reply-To: <271a33ae-b4fc-0528-cf59-5053dc46cce0@huawei.com>

On Thu, Apr 04, 2019 at 10:04:04PM +0800, YueHaibing wrote:
> +cc Rafael and linux-acpi

Yeah, but please, address my comments and send v2.

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2019-04-05 10:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190404103925.25652-1-yuehaibing@huawei.com>
2019-04-04 14:04 ` [PATCH] gpio: merrifield: Fix build err without CONFIG_ACPI YueHaibing
2019-04-05 10:07   ` Andy Shevchenko [this message]
2019-04-05 10:07     ` Andy Shevchenko
2019-04-05 12:11     ` YueHaibing
2019-04-05 12:11       ` YueHaibing
2019-04-05 14:21 ` [PATCH v2] " Yue Haibing
2019-04-05 14:21   ` Yue Haibing
2019-04-05 14:50   ` Andy Shevchenko
2019-04-05 14:50     ` Andy Shevchenko
2019-04-11 23:09     ` Rafael J. Wysocki
2019-04-11 23:09       ` Rafael J. Wysocki
2019-04-12 13:13       ` Andy Shevchenko
2019-04-12 13:13         ` Andy Shevchenko
2019-04-12 13:26         ` YueHaibing
2019-04-12 13:26           ` YueHaibing
2019-04-12 15:19   ` [PATCH v3] " Yue Haibing
2019-04-12 15:19     ` Yue Haibing
2019-04-12 17:56     ` Andy Shevchenko
2019-04-12 17:56       ` Andy Shevchenko
2019-04-23  9:17     ` Linus Walleij
2019-04-23  9:17       ` Linus Walleij
2019-04-26 12:23       ` Andy Shevchenko
2019-04-26 12:23         ` Andy Shevchenko
2019-04-29  8:40         ` Rafael J. Wysocki
2019-04-29  8:40           ` Rafael J. Wysocki

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=20190405100703.GX9224@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=yuehaibing@huawei.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