Hi! So the clocks can have different properties (frequency?), but can only be enabled/disabled together? So we can't handle them as one clock? Best regards, Pavel -- DENX Software

Hi! I just want to double check: Are the last two interrupts supposed to be same? Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235

Hi! Some comments below. ... I believe this wanted to return clk? But I'd recommend just directly returning the ERR_PTR(). ... Is "\n" missing? ... ... Should this be devm_kfree? (And is

Hi Prabhakar, I will check this series, and I am also checking the build. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/431663140 Best regards,

Thanks, applied. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

Hi Chris, I see. Thanks for the explanation. Best regards, Nobuhiro ________________________________________ 差出人: Chris Paterson <Chris.Paterson2@...> 送信日時: 2021年12月16日

Including documentation makes the build fail in buster and bullseye. Remove it. Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@...> ---

for Debian Buster. A build for Debian Bullseye can use the webserver and createfs option as the are active in the Debian provided package on salsa. Only `nodoc` needs to applied to buster and

Quirin just told me that only nodoc is needed for all. Dropping this patch again (keeping 1/2 though). Please send a v3 which does that, ie. adds a _bullseye profile and keeps the existing buster

Thanks, applied. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

From my testing only the option nodoc is necessary for bullseye. Quirin

So these things were actually broken for bullseye so far? Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

Stretch in now dropped. The conditional includes for buster is now not needed. Those includes are applicable to buster as well as bullseye. Signed-off-by: Vijai Kumar K

The generic profile of CIP Core started its work with buster, stretch was only experimental for this layer. Remove the support now. Signed-off-by: Vijai Kumar K

Changes since v1: - Change P1 commit message - Bring back conditional include of buster patch for swupdate This series has 2 patches P1 drops stretch support P2 cleans up overrides / conditional

The more accurate reasoning would be that the generic profile of CIP Core does started its work with buster, stretch was only experimental for this layer. Jan -- Siemens AG, T RDA IOT Corporate