All of lore.kernel.org
 help / color / mirror / Atom feed
From: hidehiro.kawai.ez@hitachi.com (河合英宏 / KAWAI,HIDEHIRO)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel feature support
Date: Fri, 24 Mar 2017 03:39:01 +0000	[thread overview]
Message-ID: <04EAB7311EE43145B2D3536183D1A84454EA4E9C@GSjpTKYDCembx31.service.hitachi.net> (raw)
In-Reply-To: <58C9695D.9090908@codethink.co.uk>

Hello Agustin and Ben,

> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Agustin Benito
> On 09/03/17 15:33, Ben Hutchings wrote:
> > We've previously agreed that not all kernel features (drivers,
> > filesystems, network protocols, etc.) can be supported in an SLTS
> > branch.  I'd like to start working out what the supported features
> > should be for the 4.4 branch.
> >
> > Are members able to share their kernel .config files, showing which
> > features are enabled?  Or would you prefer to specify your needs at a
> > slightly higher level?
> 
> Answering this question is important to discard features in 4.4 that are
> not of CIP interest so we can severely reduce the amount of effort that
> we will need to do in terms of fixes analysis, security etc. in the future.
> 
> Please take some time to provide feedback.

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.

Best regards,

Hidehiro Kawai
Hitachi, Ltd. Research & Development Group

-------------- next part --------------
A non-text attachment was scrubbed...
Name: defconfig
Type: application/octet-stream
Size: 12849 bytes
Desc: defconfig
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170324/94ee26b4/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: defconfig.diff
Type: application/octet-stream
Size: 20958 bytes
Desc: defconfig.diff
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170324/94ee26b4/attachment-0003.obj>

  parent reply	other threads:[~2017-03-24  3:39 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 [this message]
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
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=04EAB7311EE43145B2D3536183D1A84454EA4E9C@GSjpTKYDCembx31.service.hitachi.net \
    --to=hidehiro.kawai.ez@hitachi.com \
    --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.