From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Maintenance policies and early considerations IV
Date: Mon, 10 Oct 2016 20:05:19 +0100 [thread overview]
Message-ID: <1476126319.22569.3.camel@codethink.co.uk> (raw)
In-Reply-To: <390B4EACA1A32748BA6BC7F859F7D71655236EC1@GSjpTKYDCembx31.service.hitachi.net>
On Fri, 2016-10-07 at 07:34 +0000, ???? / KOGUCHI?TAKUO wrote:
> Hi Agustin,
> Let me understand what you wrote.
> > > CIP should avoid making any such promise because:
> > >
> > > * Upstream fixes frequently change the kernel module API and/or ABI and
> > > backporting them in a way that does not is difficult and risky - CIP
> > > users set their own kernel configurations, so there will not be a
> > > single kernel ABI for IHVs to target anyway
> >
> > Correction:
> >
> > Upstream fixes frequently change the kernel module API and/or ABI and
> > backporting them in a way that is difficult and risky - CIP users set
> > their own kernel configurations, so there will not be a single kernel ABI for IHVs to
> > target anyway
> >
>
> Is the correction correct?
The first version is what I wrote, and the correction says something I
did not mean to say.
> I thought you wrote;
> * Upstream fixes frequently change the kernel module API and/or ABI and
> backporting them in a way that does not (change the kernel module API and/or ABI )is difficult and risky - CIP
> Am I wrong?
No, you understand me rightly.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2016-10-10 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 12:59 [cip-dev] Maintenance policies and early considerations IV Agustin Benito Bethencourt
2016-09-27 8:29 ` Agustin Benito Bethencourt
2016-10-07 7:34 ` 小口琢夫 / KOGUCHI，TAKUO
2016-10-07 7:54 ` Daniel Sangorrin
2016-10-10 19:05 ` Ben Hutchings [this message]
2016-10-27 6:52 ` Hidehiro Kawai
2016-10-27 5:17 ` Jan Kiszka
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=1476126319.22569.3.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