All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel feature support
Date: Fri, 24 Mar 2017 13:16:19 +0000	[thread overview]
Message-ID: <1490361379.3749.97.camel@codethink.co.uk> (raw)
In-Reply-To: <HK2PR0601MB1329D4E7B2FC29BE6F011CFBB73F0@HK2PR0601MB1329.apcprd06.prod.outlook.com>

On Thu, 2017-03-23 at 16:32 +0000, Chris Paterson wrote:
[...]
> From an SoC vendor point of view, ideally we'd like the interfaces
> provided by the reference platform to be included. As support for our
> CIP reference platform is not yet mainlined, I can't provide the
> exact .config yet. However it will likely be very similar to
> shmobile_defconfig [1].
[...]

Thanks, I'll look through this config.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2017-03-24 13:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 14:33 [cip-dev] Kernel feature support Ben Hutchings
2017-03-09 15:25 ` Angelo Compagnucci
2017-03-09 18:55   ` Ben Hutchings
2017-03-10 12:39     ` Ben Hutchings
2017-03-15 16:18 ` Agustin Benito Bethencourt
2017-03-23 16:32   ` Chris Paterson
2017-03-24 13:16     ` Ben Hutchings [this message]
2017-03-24  3:39   ` 河合英宏 / KAWAI,HIDEHIRO
2017-03-24 13:17     ` Ben Hutchings
2017-03-27 10:31   ` Gernot Hillier
2017-03-27 11:40     ` Jan Kiszka
2017-03-28  1:28 ` Daniel Sangorrin
2017-04-12 14:25 ` Jan Kiszka
2017-04-13 10:18 ` Masato Minda
  -- strict thread matches above, loose matches on Subject: below --
2018-03-31  7:56 Wes Huang (黃淵河)
2018-04-02  3:19 ` Daniel Sangorrin
2018-04-02  5:34   ` Wes Huang (黃淵河)
2018-04-02  5:04 ` Zoran S
2018-04-04 17:48 ` Ben Hutchings
2018-10-04 14:43 ` Ben Hutchings

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=1490361379.3749.97.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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.