From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
David Cohen <david.a.cohen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio-langwell: remove Withney point support
Date: Thu, 20 Jun 2013 11:02:12 +0300 [thread overview]
Message-ID: <20130620080212.GO11878@intel.com> (raw)
In-Reply-To: <CAHp75VdqOTUtp=LEN8hbxJq1E2-BxhxVW0BtHUYhW=-4soYqsQ@mail.gmail.com>
On Thu, Jun 20, 2013 at 10:09:37AM +0300, Andy Shevchenko wrote:
> On Thu, Jun 20, 2013 at 9:46 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Wed, Jun 19, 2013 at 11:02 PM, Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> >> On Wed, Jun 19, 2013 at 10:23 PM, Linus Walleij
> >> <linus.walleij@linaro.org> wrote:
> >>
> >>> Please give some context though, Wikipedia says:
> >>>
> >>> Whitney Point is the codename of a PCH in the Oak Trail platform
> >>> chipset for Atom Lincroft microprocessors.
> >>> This has the following variations:
> >>> 82SM35 (PCH SM35)
> >>
> >>> Does this mean that platform is not coming back to support Linux
> >>> ever again
> >>
> >> I think it's very unluckily.
> >> May be David could shed a light...
> >
> > Is that some kind of NACK?
>
> No, the opposite.
> I meant it's very unluckily that we will have any Oak Trail user in future.
You mean *unlikely*, right?
AFAICT there are no real Oak Trail products outside Intel. It was
superseded by Medfield.
next prev parent reply other threads:[~2013-06-20 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 6:43 [PATCH] gpio-langwell: remove Withney point support Andy Shevchenko
2013-06-19 19:23 ` Linus Walleij
2013-06-19 21:02 ` Andy Shevchenko
2013-06-20 6:46 ` Linus Walleij
2013-06-20 7:09 ` Andy Shevchenko
2013-06-20 8:02 ` Mika Westerberg [this message]
2013-06-20 8:40 ` Linus Walleij
2013-06-21 0:48 ` David Cohen
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=20130620080212.GO11878@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=david.a.cohen@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.