public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/4] ACPI / LPSS: clock improvements
Date: Tue, 2 Sep 2014 13:46:45 +0300	[thread overview]
Message-ID: <20140902104645.GP5466@lahna.fi.intel.com> (raw)
In-Reply-To: <1409644510-26397-1-git-send-email-heikki.krogerus@linux.intel.com>

On Tue, Sep 02, 2014 at 10:55:06AM +0300, Heikki Krogerus wrote:
> Minor improvements mainly related to how the clocks are handled.
> 
> 
> Heikki Krogerus (4):
>   ACPI / LPSS: introduce flags
>   ACPI / LPSS: drop clkdev_name member from lpss_device_desc
>   ACPI / LPSS: support for 133MHz I2C source clock on Baytrail
>   ACPI / LPSS: remove struct lpss_shared_clock
> 

Nice cleanup!

Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>

for the whole series.

  parent reply	other threads:[~2014-09-02 10:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  7:55 [PATCH 0/4] ACPI / LPSS: clock improvements Heikki Krogerus
2014-09-02  7:55 ` [PATCH 1/4] ACPI / LPSS: introduce flags Heikki Krogerus
2014-09-02  8:45   ` Andy Shevchenko
2014-09-02  7:55 ` [PATCH 2/4] ACPI / LPSS: drop clkdev_name member from lpss_device_desc Heikki Krogerus
2014-09-02  8:43   ` Andy Shevchenko
2014-09-02 10:34     ` Heikki Krogerus
2014-09-02 10:42       ` Andy Shevchenko
2014-09-02  7:55 ` [PATCH 3/4] ACPI / LPSS: support for 133MHz I2C source clock on Baytrail Heikki Krogerus
2014-09-02  7:55 ` [PATCH 4/4] ACPI / LPSS: remove struct lpss_shared_clock Heikki Krogerus
2014-09-02  8:47   ` Andy Shevchenko
2014-09-02 10:46 ` Mika Westerberg [this message]
2014-09-03 21:49 ` [PATCH 0/4] ACPI / LPSS: clock improvements 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=20140902104645.GP5466@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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