From: Mark Brown <broonie@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Bird, Tim" <Tim.Bird@sony.com>,
Linus Walleij <linus.walleij@linaro.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Greg KH <gregkh@linuxfoundation.org>,
Dan Williams <dan.j.williams@intel.com>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: [MAINTAINERS SUMMIT] Between a rock and a hard place, managing expectations...
Date: Thu, 24 Aug 2023 20:58:12 +0100 [thread overview]
Message-ID: <ZOe2VIuCkmal5YpV@finisterre.sirena.org.uk> (raw)
In-Reply-To: <6c140552-9c1c-5038-35b3-443d60de31f1@acm.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Thu, Aug 24, 2023 at 12:29:34PM -0700, Bart Van Assche wrote:
> The GKI indeed makes changes to the core kernel harder after its API has
> been frozen. Does carrier certification really require changes to the core
> kernel?
I don't know anything about the issue Tim was facing but I've definitely
run into issues during testing which were best fixed by extending the
core, sometimes it's not a straight bug in the core (which I'd guess
should be relatively easy to get a backport for, you can probably just
go via upstream stable) but rather that this is the appropriate layer to
handle whatever the issue is. Teach the core about a concept, then tell
the core that your device does the thing which you've discovered needs
to be handled.
Note that I've got no experience working with GKI here, but unless
things have changed a lot there's not really any phase of the process
where there isn't substantial time pressure.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-08-24 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 0:43 [MAINTAINERS SUMMIT] Between a rock and a hard place, managing expectations Dan Williams
2023-08-22 8:55 ` Greg KH
2023-08-22 13:37 ` Linus Walleij
2023-08-22 14:29 ` Laurent Pinchart
2023-08-24 0:46 ` Jason Gunthorpe
2023-08-24 8:16 ` Linus Walleij
2023-08-24 14:19 ` Jason Gunthorpe
2023-08-24 17:12 ` Mark Brown
2023-08-24 17:20 ` Bird, Tim
2023-08-24 19:29 ` Bart Van Assche
2023-08-24 19:58 ` Mark Brown [this message]
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=ZOe2VIuCkmal5YpV@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=Tim.Bird@sony.com \
--cc=bvanassche@acm.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@nvidia.com \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).