linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Andy Shevchenko
	<andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	David Cohen
	<david.a.cohen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	Jarkko Nikula
	<jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [PATCH v2 3/4] i2c: designware-pci: no need to provide clk_khz
Date: Fri, 23 Jan 2015 15:36:47 +0100	[thread overview]
Message-ID: <20150123143647.GC9592@katana> (raw)
In-Reply-To: <1422014045-20584-3-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

On Fri, Jan 23, 2015 at 01:54:04PM +0200, Andy Shevchenko wrote:
> The clk_khz field makes sense only if SS counters are not provided. Since we
> provide them for Haswell and Baytrail explicitly we may omit the clk_khz
> parameter.
> 
> Reviewed-by: Jarkko Nikula <jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>

Applied to for-next, thanks!


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-01-23 14:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 11:54 [PATCH v2 1/4] i2c: designware-pci: remove Moorestown support Andy Shevchenko
     [not found] ` <1422014045-20584-1-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-23 11:54   ` [PATCH v2 2/4] i2c: designware-pci: shrink dw_pci_controllers array Andy Shevchenko
     [not found]     ` <1422014045-20584-2-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-23 12:41       ` Wolfram Sang
2015-01-23 12:48         ` Mika Westerberg
     [not found]           ` <20150123124805.GP1850-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2015-01-23 13:04             ` Andy Shevchenko
     [not found]               ` <1422018246.31903.162.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-24  4:19                 ` Wolfram Sang
2015-01-26 12:15                   ` Wolfram Sang
2015-02-05 19:21                     ` Wolfram Sang
2015-02-05 22:56                       ` David Cohen
     [not found]                         ` <20150205225651.GA1022-UmZa8NLUsbhHELxPJs4m+1DQ4js95KgL@public.gmane.org>
2015-02-06 10:50                           ` Andy Shevchenko
2015-01-23 11:54   ` [PATCH v2 3/4] i2c: designware-pci: no need to provide clk_khz Andy Shevchenko
     [not found]     ` <1422014045-20584-3-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-23 14:36       ` Wolfram Sang [this message]
2015-01-23 11:54   ` [PATCH v2 4/4] i2c: designware-pci: update Intel copyright line Andy Shevchenko
2015-01-23 14:35   ` [PATCH v2 1/4] i2c: designware-pci: remove Moorestown support Wolfram Sang

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=20150123143647.GC9592@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=david.a.cohen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).