From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel feature support
Date: Thu, 09 Mar 2017 18:55:47 +0000 [thread overview]
Message-ID: <1489085747.2949.78.camel@codethink.co.uk> (raw)
In-Reply-To: <CA+TH9VmBs6kZ6x+j=2i_caGAVa3oHggxYH8NEtriB6ygP8H3zA@mail.gmail.com>
On Thu, 2017-03-09 at 16:25 +0100, Angelo Compagnucci wrote:
> Dear Ben Hutchings,
>
> 2017-03-09 15:33 GMT+01:00 Ben Hutchings <ben.hutchings@codethink.co.uk>:
> > 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?
>
> I would really like to have IIO drivers, they are generally easy to
> backport and extremely useful in industrial contexts.
But you don't use *all* the IIO drivers, do you?
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2017-03-09 18:55 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 [this message]
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
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=1489085747.2949.78.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