public inbox for cip-dev@lists.cip-project.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:17:11 +0000	[thread overview]
Message-ID: <1490361431.3749.98.camel@codethink.co.uk> (raw)
In-Reply-To: <04EAB7311EE43145B2D3536183D1A84454EA4E9C@GSjpTKYDCembx31.service.hitachi.net>

On Fri, 2017-03-24 at 03:39 +0000, ???? / KAWAI?HIDEHIRO wrote:
[...]
> I attached a defconfig for one of our products running on 4.4.12.
> This config is based on omap2plus_defconfig, and a diff from
> omap2plus_defconfig is also attached.
>
> Currently, each config item has not been prioritized yet, and it
> may contain non-important items.  Please treat our defconfig
> as a reference at this point.

Thanks, this is useful.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2017-03-24 13:17 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
2017-03-24  3:39   ` 河合英宏 / KAWAI,HIDEHIRO
2017-03-24 13:17     ` Ben Hutchings [this message]
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=1490361431.3749.98.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox