public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Colin King <colin.king@canonical.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: intel-lpss: remove spt_info, it is not used
Date: Wed, 24 Feb 2016 13:29:37 +0200	[thread overview]
Message-ID: <1456313377.13244.61.camel@linux.intel.com> (raw)
In-Reply-To: <1456266139-26409-1-git-send-email-colin.king@canonical.com>

On Tue, 2016-02-23 at 22:22 +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> spt_info is not used at all, I suspect it is vestigial code left
> over when the intel-lpss-acpi was derived from intel-lpss-pci
> 

No objections from me. Anyway, we can find in the Git log if we need it
in the future.

Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/mfd/intel-lpss-acpi.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/drivers/mfd/intel-lpss-acpi.c b/drivers/mfd/intel-lpss-
> acpi.c
> index 06f00d6..e072dc9 100644
> --- a/drivers/mfd/intel-lpss-acpi.c
> +++ b/drivers/mfd/intel-lpss-acpi.c
> @@ -22,10 +22,6 @@
>  
>  #include "intel-lpss.h"
>  
> -static const struct intel_lpss_platform_info spt_info = {
> -	.clk_rate = 120000000,
> -};
> -
>  static struct property_entry spt_i2c_properties[] = {
>  	PROPERTY_ENTRY_U32("i2c-sda-hold-time-ns", 230),
>  	{ },

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2016-02-24 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 22:22 [PATCH] mfd: intel-lpss: remove spt_info, it is not used Colin King
2016-02-24 11:29 ` Andy Shevchenko [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=1456313377.13244.61.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=colin.king@canonical.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox