linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Cohen <david.a.cohen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Andy Shevchenko
	<andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Jarkko Nikula
	<jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [PATCH v1 1/3] i2c: designware-pci: shrink dw_pci_controllers array
Date: Fri, 23 Jan 2015 10:56:51 -0800	[thread overview]
Message-ID: <20150123185651.GA1739@psi-dev26.jf.intel.com> (raw)
In-Reply-To: <20150123175044.GA14183-UmZa8NLUsbhHELxPJs4m+1DQ4js95KgL@public.gmane.org>

On Fri, Jan 23, 2015 at 09:50:44AM -0800, David Cohen wrote:
> On Fri, Jan 23, 2015 at 01:57:29PM +0200, Andy Shevchenko wrote:
> > On Thu, 2015-01-22 at 14:27 -0800, David Cohen wrote:
> > > On Thu, Jan 22, 2015 at 08:17:58PM +0100, Wolfram Sang wrote:
> > > > 
> > > > > Since you're doing this rework, could you remove moorestown for good?
> > > > > It's no longer supported as one of intel mid's platform anyway.
> > > > 
> > > > If support for that platform is not broken anyhow, I'd say let's keep
> > > > it. There still might be users out there...
> > > > 
> > > 
> > > It actually is. When Medfield, Clover Trail and Merrifield support was
> > > merged, Moorefield support became broken with no interest from anybody
> > > to fix it. It's time now to remove all of its code :)
> > 
> > You perhaps meant Moorestown.
> 
> Oops. Sorry for the typo. Yes, I meant Morrestown :)

Grrr... Moorestown :)

> 
> Br, David

      parent reply	other threads:[~2015-01-23 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 14:44 [PATCH v1 1/3] i2c: designware-pci: shrink dw_pci_controllers array Andy Shevchenko
     [not found] ` <1421937869-28376-1-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-22 14:44   ` [PATCH v1 2/3] i2c: designware-pci: update Intel copytight line Andy Shevchenko
2015-01-22 14:44   ` [PATCH v1 3/3] i2c: designware-pci: no need to provide clk_khz Andy Shevchenko
     [not found]     ` <1421937869-28376-3-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-23  9:12       ` Jarkko Nikula
2015-01-22 19:03   ` [PATCH v1 1/3] i2c: designware-pci: shrink dw_pci_controllers array David Cohen
     [not found]     ` <20150122190301.GA15297-UmZa8NLUsbhHELxPJs4m+1DQ4js95KgL@public.gmane.org>
2015-01-22 19:17       ` Wolfram Sang
2015-01-22 22:27         ` David Cohen
     [not found]           ` <20150122222712.GA3678-UmZa8NLUsbhHELxPJs4m+1DQ4js95KgL@public.gmane.org>
2015-01-23 11:57             ` Andy Shevchenko
     [not found]               ` <1422014249.31903.159.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-23 17:50                 ` David Cohen
     [not found]                   ` <20150123175044.GA14183-UmZa8NLUsbhHELxPJs4m+1DQ4js95KgL@public.gmane.org>
2015-01-23 18:56                     ` David Cohen [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=20150123185651.GA1739@psi-dev26.jf.intel.com \
    --to=david.a.cohen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
    --cc=andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@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).