From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel feature support - filesystems and networking
Date: Mon, 29 May 2017 04:58:30 +0100 [thread overview]
Message-ID: <592B9C66.709@codethink.co.uk> (raw)
In-Reply-To: <390B4EACA1A32748BA6BC7F859F7D71656BF302D@GSjpTKYDCembx32.service.hitachi.net>
Hi Ben,
On 29/05/17 03:40, ???? / KOGUCHI?TAKUO wrote:
> Hi Ben,
>
> Thanks for your efforts.
>
>> - overlayfs (CONFIG_OVERLAY_FS)
>> - I found many apparently important bug fixes in later kernel
versions that have not been backported
Is there a technical reason for these patches not being backported or is
it simply that never was requested/needed before?
> OVERLAY_FS is one of the features Hitachi wants to use.
> I hope you look into this further and I would like to know if other members also want it.
Based on this request, is it possible for you to estimate the effort to
do this?
@Takuo is there a kernel developer from Hitachi that would be willing to
work under Ben's supervision/review in backporting these patches?
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2017-05-29 3:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 2:13 [cip-dev] Kernel feature support - filesystems and networking Ben Hutchings
2017-05-29 2:40 ` 小口琢夫 / KOGUCHI，TAKUO
2017-05-29 3:58 ` Agustin Benito Bethencourt [this message]
2017-05-31 10:17 ` Ben Hutchings
2017-05-29 5:36 ` Jan Kiszka
2017-05-31 10:15 ` Ben Hutchings
2017-06-01 13:30 ` Daniel Sangorrin
2017-06-01 13:49 ` Jan Kiszka
2017-06-02 2:36 ` Daniel Sangorrin
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=592B9C66.709@codethink.co.uk \
--to=agustin.benito@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