From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [PATCH 1/3] cobalt uapi: Introducing new feature flag for settime64 availability References: <1229be33-848d-ab5b-d6dd-1b7ae38d36f9@siemens.com> <20201113115932.276959-1-florian.bezdeka@siemens.com> <20201113115932.276959-2-florian.bezdeka@siemens.com> <0ea225343dac0d572f968955af1ebff988a210ef.camel@siemens.com> From: Jan Kiszka Message-ID: Date: Sat, 14 Nov 2020 08:33:52 +0100 MIME-Version: 1.0 In-Reply-To: <0ea225343dac0d572f968955af1ebff988a210ef.camel@siemens.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Bezdeka, Florian (T RDA IOT SES-DE)" , "xenomai@xenomai.org" , "chensong@tj.kylinos.cn" On 13.11.20 17:18, Bezdeka, Florian (T RDA IOT SES-DE) wrote: > On Fri, 2020-11-13 at 14:25 +0100, Jan Kiszka wrote: >> On 13.11.20 13:00, florian.bezdeka--- via Xenomai wrote: >>> From: Florian Bezdeka >>> >>> Adding a new feature flag to allow the library asking for settime64 >>> support. That will allow the library to use the new system call if >>> it >>> is available / supported by the kernel. >>> >> >> As proposed in the other thread, we should state that this flag is >> supposed to be dropped on the next major ABI revision update. > > I agree. The ABI revision of all supported architectures has to be > incremented when removing this flag. > > How do we make sure that the necessary steps are taken once the next > major release process starts? Is there some kind of "next major branch" > available where we could apply patches to after settime64 stuff was > merged to "next"? next and master are currently "stable 3.1.x". There is no branch for a next major release yet. But you could leave a comment at a line that defines the ABI revision and, thus, needs to be touched on next bump. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux