public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, Lee Jones <lee.jones@linaro.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] ACPI / PMIC: Add Cherry Trail Crystal Cove PMIC OpRegion driver
Date: Fri, 25 Oct 2019 12:34:32 +0300	[thread overview]
Message-ID: <20191025093432.GL32742@smile.fi.intel.com> (raw)
In-Reply-To: <230f4820-688f-4b04-ee62-771486fcfa63@redhat.com>

On Fri, Oct 25, 2019 at 11:06:40AM +0200, Hans de Goede wrote:
> On 25-10-2019 09:45, Andy Shevchenko wrote:
> > On Thu, Oct 24, 2019 at 11:38:26PM +0200, Hans de Goede wrote:

> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > 
> > as long as name pattern uses "chtcc".
> 
> As I already replied to your other similar remark, I would really like to
> stick with crc, crc to me means either crystal-cove or well a crc, cc triggers
> different associations in my mind. Also other crystal-cove files also use crc
> in their filename.

Okay, let's stick with crc for this one.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2019-10-25  9:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 21:38 [PATCH 1/4] ACPI / PMIC: Add partial support for Cherry Trail Crystal Cove PMIC Hans de Goede
2019-10-24 21:38 ` [PATCH 1/4] ACPI / PMIC: Do not register handlers for unhandled OpRegions Hans de Goede
2019-10-25  7:42   ` Andy Shevchenko
2019-10-24 21:38 ` [PATCH 2/4] ACPI / PMIC: Add byt prefix to Crystal Cove PMIC OpRegion driver Hans de Goede
2019-10-25  7:41   ` Andy Shevchenko
2019-10-25  7:48     ` Andy Shevchenko
2019-10-25  8:59     ` Hans de Goede
2019-10-25  9:33       ` Andy Shevchenko
2019-10-25  9:49         ` Rafael J. Wysocki
2019-10-24 21:38 ` [PATCH 3/4] ACPI / PMIC: Add Cherry Trail " Hans de Goede
2019-10-25  7:45   ` Andy Shevchenko
2019-10-25  9:06     ` Hans de Goede
2019-10-25  9:34       ` Andy Shevchenko [this message]
2019-10-24 21:38 ` [PATCH 4/4] mfd: intel_soc_pmic_crc: Add "cht_crystal_cove_pmic" cell to CHT cells Hans de Goede
2019-10-25  7:47   ` Andy Shevchenko
2019-11-01  9:01   ` Lee Jones
2019-11-05 23:11     ` 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=20191025093432.GL32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=lee.jones@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --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