Date   

Re: [PATCH] drm: of: Fix linking when CONFIG_OF is not set

Pavel Machek
 

On Thu 2020-08-13 06:39:55, Biju Das wrote:
Hi Pavel,

Thanks for the feedback.

Subject: Re: [PATCH] drm: of: Fix linking when CONFIG_OF is not set

Hi!

I assume this patch is for 4.19-cip?
Yes, it is for 4.19-cip.

commit 528d06d41b80a4acb2a9efd33bfc87495147f75e upstream.

The new helper drm_of_lvds_get_dual_link_pixel_order() introduced in
commit 6529007522de has a fallback stub when CONFIG_OF is not set, but
the stub is declared in drm_of.h without a static inline. This causes
multiple definitions of the function to be linked when the CONFIG_OF
option isn't set. Fix it by making the stub static inline.
So this is pretty obvious, and I'll likely apply it.
Thanks for applying it.
Applied.
Pavel

--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


[PATCH 4.19.y-cip 2/2] drm: atomic helper: fix W=1 warnings

Biju Das <biju.das.jz@...>
 

From: Benjamin Gaignard <benjamin.gaignard@st.com>

commit bf5d837a0a4ced7cc223befc9e76d4ad30697d27 upstream.

Few for_each macro set variables that are never used later which led
to generate unused-but-set-variable warnings.
Add (void)(foo) inside the macros to remove these warnings

Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20191008124254.2144-1-benjamin.gaignard@st.com
Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
---
include/drm/drm_atomic.h | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h
index 6329ed4af310..9042fdae9211 100644
--- a/include/drm/drm_atomic.h
+++ b/include/drm/drm_atomic.h
@@ -662,6 +662,7 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->connectors[__i].ptr && \
((connector) = (__state)->connectors[__i].ptr, \
+ (void)(connector) /* Only to avoid unused-but-set-variable warning */, \
(old_connector_state) = (__state)->connectors[__i].old_state, \
(new_connector_state) = (__state)->connectors[__i].new_state, 1))

@@ -683,6 +684,7 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->connectors[__i].ptr && \
((connector) = (__state)->connectors[__i].ptr, \
+ (void)(connector) /* Only to avoid unused-but-set-variable warning */, \
(old_connector_state) = (__state)->connectors[__i].old_state, 1))

/**
@@ -703,7 +705,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->connectors[__i].ptr && \
((connector) = (__state)->connectors[__i].ptr, \
- (new_connector_state) = (__state)->connectors[__i].new_state, 1))
+ (void)(connector) /* Only to avoid unused-but-set-variable warning */, \
+ (new_connector_state) = (__state)->connectors[__i].new_state, \
+ (void)(new_connector_state) /* Only to avoid unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_crtc_in_state - iterate over all CRTCs in an atomic update
@@ -723,7 +727,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->crtcs[__i].ptr && \
((crtc) = (__state)->crtcs[__i].ptr, \
+ (void)(crtc) /* Only to avoid unused-but-set-variable warning */, \
(old_crtc_state) = (__state)->crtcs[__i].old_state, \
+ (void)(old_crtc_state) /* Only to avoid unused-but-set-variable warning */, \
(new_crtc_state) = (__state)->crtcs[__i].new_state, 1))

/**
@@ -762,7 +768,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->crtcs[__i].ptr && \
((crtc) = (__state)->crtcs[__i].ptr, \
- (new_crtc_state) = (__state)->crtcs[__i].new_state, 1))
+ (void)(crtc) /* Only to avoid unused-but-set-variable warning */, \
+ (new_crtc_state) = (__state)->crtcs[__i].new_state, \
+ (void)(new_crtc_state) /* Only to avoid unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_plane_in_state - iterate over all planes in an atomic update
@@ -782,6 +790,7 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->planes[__i].ptr && \
((plane) = (__state)->planes[__i].ptr, \
+ (void)(plane) /* Only to avoid unused-but-set-variable warning */, \
(old_plane_state) = (__state)->planes[__i].old_state,\
(new_plane_state) = (__state)->planes[__i].new_state, 1))

@@ -842,7 +851,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->planes[__i].ptr && \
((plane) = (__state)->planes[__i].ptr, \
- (new_plane_state) = (__state)->planes[__i].new_state, 1))
+ (void)(plane) /* Only to avoid unused-but-set-variable warning */, \
+ (new_plane_state) = (__state)->planes[__i].new_state, \
+ (void)(new_plane_state) /* Only to avoid unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_private_obj_in_state - iterate over all private objects in an atomic update
--
2.17.1


[PATCH 4.19.y-cip 1/2] drm: Add drm_atomic_get_old/new_private_obj_state

Biju Das <biju.das.jz@...>
 

From: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>

commit 9801a7eadf4cc29cdc90583a49f12decbb832ced upstream.

This pair of functions return the old/new private object state for the
given private_obj, or NULL if the private_obj is not part of the global
atomic state.

Reviewed-by: Alexandru Gheorghe <alexandru-cosmin.gheorghe@arm.com>
Signed-off-by: James Qian Wang (Arm Technology China) <james.qian.wang@arm.com>
Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
[removed changes in drivers/gpu/drm/drm_atomic.c, since the same changes
are already present as part of the commit 60b4667275b6]
---
include/drm/drm_atomic.h | 6 ++++++
1 file changed, 6 insertions(+)

diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h
index c0b48e25a620..6329ed4af310 100644
--- a/include/drm/drm_atomic.h
+++ b/include/drm/drm_atomic.h
@@ -402,6 +402,12 @@ void drm_atomic_private_obj_fini(struct drm_private_obj *obj);
struct drm_private_state * __must_check
drm_atomic_get_private_obj_state(struct drm_atomic_state *state,
struct drm_private_obj *obj);
+struct drm_private_state *
+drm_atomic_get_old_private_obj_state(struct drm_atomic_state *state,
+ struct drm_private_obj *obj);
+struct drm_private_state *
+drm_atomic_get_new_private_obj_state(struct drm_atomic_state *state,
+ struct drm_private_obj *obj);

struct drm_connector *
drm_atomic_get_old_connector_for_encoder(struct drm_atomic_state *state,
--
2.17.1


Re: [linux-cip:linux-4.19.y-cip 7/17] drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for 'drm_atomic_get_old_private_obj_state'

Biju Das <biju.das.jz@...>
 

Hi Pavel,

Thanks for the feedback.

drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for
'drm_atomic_get_old_private_obj_state'

Hi!

I have received a warning message mail from Kernel test robot. I have
investigated this issue and found there were lots of warnings with
architecture by following the steps mentioned in this mail.

Then I investigated this particular issue and found that issue is
caused by bad commit done by me while backporting. The below backport
commit has extra functions from patch1(0001-drm-Add-
drm_atomic_get_old-new_private_obj_state.patch), but the corresponding
header is missing.

cip commit: cacc2a81b9872aa8830353110b1252021f124ae8
upstream commit: 1b27fbdde1df172dba604855c45078d741f8c858

I have attached 3 patches, that looks like fixes the issue mentioned by
kernel robot.

How do we proceed here?
drop cip commit: cacc2a81b9872aa8830353110b1252021f124ae8 and apply
the 3 patches to fix this issue?
No, let's not revert anything.

This is trivial fix for first issue, make it into patch:
Ok, will make it into a patch

diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h index
c0b48e25a620..9042fdae9211 100644
--- a/include/drm/drm_atomic.h
+++ b/include/drm/drm_atomic.h
@@ -402,6 +402,12 @@ void drm_atomic_private_obj_fini(struct
drm_private_obj *obj); struct drm_private_state * __must_check
drm_atomic_get_private_obj_state(struct drm_atomic_state *state,
struct drm_private_obj *obj);
+struct drm_private_state *
+drm_atomic_get_old_private_obj_state(struct drm_atomic_state *state,
+ struct drm_private_obj *obj);
+struct drm_private_state *
+drm_atomic_get_new_private_obj_state(struct drm_atomic_state *state,
+ struct drm_private_obj *obj);

struct drm_connector *
drm_atomic_get_old_connector_for_encoder(struct drm_atomic_state
*state,

And this is somehow strange / non-trivial thingie. Make it into second patch,
and maybe try to explain what is going on there.
Ok will do.

Cheers,
Biju


@@ -656,6 +662,7 @@ void drm_state_dump(struct drm_device *dev, struct
drm_printer *p);
(__i)++)
\
for_each_if ((__state)->connectors[__i].ptr &&
\
((connector) = (__state)->connectors[__i].ptr,
\
+ (void)(connector) /* Only to avoid unused-but-
set-variable
+warning */, \
(old_connector_state) = (__state)-
connectors[__i].old_state,\
(new_connector_state) = (__state)-
connectors[__i].new_state, 1))
@@ -677,6 +684,7 @@ void drm_state_dump(struct drm_device *dev, struct
drm_printer *p);
(__i)++)
\
for_each_if ((__state)->connectors[__i].ptr &&
\
((connector) = (__state)->connectors[__i].ptr,
\
+ (void)(connector) /* Only to avoid unused-but-
set-variable
+warning */, \
(old_connector_state) = (__state)-
connectors[__i].old_state, 1))
/**
@@ -697,7 +705,9 @@ void drm_state_dump(struct drm_device *dev, struct
drm_printer *p);
(__i)++)
\
for_each_if ((__state)->connectors[__i].ptr &&
\
((connector) = (__state)->connectors[__i].ptr,
\
- (new_connector_state) = (__state)-
connectors[__i].new_state, 1))
+ (void)(connector) /* Only to avoid unused-but-
set-variable warning */, \
+ (new_connector_state) = (__state)-
connectors[__i].new_state, \
+ (void)(new_connector_state) /* Only to avoid
+unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_crtc_in_state - iterate over all CRTCs in an atomic
update @@ -717,7 +727,9 @@ void drm_state_dump(struct drm_device
*dev, struct drm_printer *p);
(__i)++)\
for_each_if ((__state)->crtcs[__i].ptr &&\
((crtc) = (__state)->crtcs[__i].ptr,\
+ (void)(crtc) /* Only to avoid unused-but-set-
variable warning
+*/, \
(old_crtc_state) = (__state)->crtcs[__i].old_state,
\
+ (void)(old_crtc_state) /* Only to avoid unused-
but-set-variable
+warning */, \
(new_crtc_state) = (__state)-
crtcs[__i].new_state, 1))
/**
@@ -756,7 +768,9 @@ void drm_state_dump(struct drm_device *dev, struct
drm_printer *p);
(__i)++)\
for_each_if ((__state)->crtcs[__i].ptr &&\
((crtc) = (__state)->crtcs[__i].ptr,\
- (new_crtc_state) = (__state)-
crtcs[__i].new_state, 1))
+ (void)(crtc) /* Only to avoid unused-but-set-
variable warning */, \
+ (new_crtc_state) = (__state)-
crtcs[__i].new_state, \
+ (void)(new_crtc_state) /* Only to avoid unused-
but-set-variable
+warning */, 1))

/**
* for_each_oldnew_plane_in_state - iterate over all planes in an atomic
update @@ -776,6 +790,7 @@ void drm_state_dump(struct drm_device
*dev, struct drm_printer *p);
(__i)++)\
for_each_if ((__state)->planes[__i].ptr &&\
((plane) = (__state)->planes[__i].ptr,\
+ (void)(plane) /* Only to avoid unused-but-set-
variable warning
+*/, \
(old_plane_state) = (__state)-
planes[__i].old_state,\
(new_plane_state) = (__state)-
planes[__i].new_state, 1))
@@ -836,7 +851,9 @@ void drm_state_dump(struct drm_device *dev, struct
drm_printer *p);
(__i)++)\
for_each_if ((__state)->planes[__i].ptr &&\
((plane) = (__state)->planes[__i].ptr,\
- (new_plane_state) = (__state)-
planes[__i].new_state, 1))
+ (void)(plane) /* Only to avoid unused-but-set-
variable warning */, \
+ (new_plane_state) = (__state)-
planes[__i].new_state, \
+ (void)(new_plane_state) /* Only to avoid
+unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_private_obj_in_state - iterate over all private objects in
an atomic update



--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Renesas Electronics Europe GmbH, Geschaeftsfuehrer/President: Carsten Jauch, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany, Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647


Re: [linux-cip:linux-4.19.y-cip 7/17] drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for 'drm_atomic_get_old_private_obj_state'

Biju Das <biju.das.jz@...>
 

Hi Pavel,

Thanks for the feedback.

drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for
'drm_atomic_get_old_private_obj_state'

Hi!

I have received a warning message mail from Kernel test robot. I have
investigated this issue and found there were lots of warnings with
architecture by following the steps mentioned in this mail.

Then I investigated this particular issue and found that issue is
caused by bad commit done by me while backporting. The below backport
commit has extra functions from patch1(0001-drm-Add-
drm_atomic_get_old-new_private_obj_state.patch), but the corresponding
header is missing.

cip commit: cacc2a81b9872aa8830353110b1252021f124ae8
upstream commit: 1b27fbdde1df172dba604855c45078d741f8c858

I have attached 3 patches, that looks like fixes the issue mentioned by
kernel robot.

How do we proceed here?
drop cip commit: cacc2a81b9872aa8830353110b1252021f124ae8 and apply
the 3 patches to fix this issue?
First I want to make sure: we are talking about commit
60b4667275b60d92c760d48df95f5b80bbcfde6e? Because I don't see
cacc2a81b9872aa8830353110b1252021f124ae8 around.
Yes, I am talking about 60b4667275b60d92c760d48df95f5b80bbcfde6e.

Cheers,
Biju



Renesas Electronics Europe GmbH, Geschaeftsfuehrer/President: Carsten Jauch, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany, Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647


[PATCH 4.4.y-cip] ARM: shmobile: defconfig: Restore debugfs support

Biju Das <biju.das.jz@...>
 

From: Geert Uytterhoeven <geert+renesas@glider.be>

commit fa2cdb1762d15f701b83efa60b04f0d04e71bf89 upstream.

Since commit 0e4a459f56c32d3e ("tracing: Remove unnecessary DEBUG_FS
dependency"), CONFIG_DEBUG_FS is no longer auto-enabled. This breaks
booting Debian 9, as systemd needs debugfs:

[FAILED] Failed to mount /sys/kernel/debug.
See 'systemctl status sys-kernel-debug.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
...
You are in emergGive root password for maintenance
(or press Control-D to continue):

Fix this by enabling CONFIG_DEBUG_FS explicitly.

See also commit 18977008f44c66bd ("ARM: multi_v7_defconfig: Restore
debugfs support").

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Link: https://lore.kernel.org/r/20191209101327.26571-1-geert+renesas@glider.be
Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
---
arch/arm/configs/shmobile_defconfig | 1 +
1 file changed, 1 insertion(+)

diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 151fad5c0b8d..865d1696109f 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -226,3 +226,4 @@ CONFIG_NLS_ISO8859_1=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
# CONFIG_ARM_UNWIND is not set
+CONFIG_DEBUG_FS=y
--
2.17.1


Re: [PATCH] drm: of: Fix linking when CONFIG_OF is not set

Biju Das <biju.das.jz@...>
 

Hi Pavel,

Thanks for the feedback.

Subject: Re: [PATCH] drm: of: Fix linking when CONFIG_OF is not set

Hi!

I assume this patch is for 4.19-cip?
Yes, it is for 4.19-cip.

commit 528d06d41b80a4acb2a9efd33bfc87495147f75e upstream.

The new helper drm_of_lvds_get_dual_link_pixel_order() introduced in
commit 6529007522de has a fallback stub when CONFIG_OF is not set, but
the stub is declared in drm_of.h without a static inline. This causes
multiple definitions of the function to be linked when the CONFIG_OF
option isn't set. Fix it by making the stub static inline.
So this is pretty obvious, and I'll likely apply it.
Thanks for applying it.

Regards,
Biju

Best regards,
Pavel


diff --git a/include/drm/drm_of.h b/include/drm/drm_of.h index
8ec7ca6d2369..b9b093add92e 100644
--- a/include/drm/drm_of.h
+++ b/include/drm/drm_of.h
@@ -92,8 +92,9 @@ static inline int drm_of_find_panel_or_bridge(const
struct device_node *np,
return -EINVAL;
}

-int drm_of_lvds_get_dual_link_pixel_order(const struct device_node
*port1,
- const struct device_node *port2)
+static inline int
+drm_of_lvds_get_dual_link_pixel_order(const struct device_node
*port1,
+ const struct device_node *port2)
{
return -EINVAL;
}
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Renesas Electronics Europe GmbH, Geschaeftsfuehrer/President: Carsten Jauch, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany, Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647


Re: [PATCH 4.4.y-cip] ARM: shmobile: defconfig: Restore debugfs support

Pavel Machek
 

Hi!

From: Geert Uytterhoeven <geert+renesas@glider.be>

commit fa2cdb1762d15f701b83efa60b04f0d04e71bf89 upstream.

Since commit 0e4a459f56c32d3e ("tracing: Remove unnecessary DEBUG_FS
dependency"), CONFIG_DEBUG_FS is no longer auto-enabled. This breaks
booting Debian 9, as systemd needs debugfs:

[FAILED] Failed to mount /sys/kernel/debug.
See 'systemctl status sys-kernel-debug.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
...
You are in emergGive root password for maintenance
(or press Control-D to continue):

Fix this by enabling CONFIG_DEBUG_FS explicitly.

See also commit 18977008f44c66bd ("ARM: multi_v7_defconfig: Restore
debugfs support").
Do we rely on these defconfigs? I can take it as it should not break
anything, but it should not really be too important for -cip project.

[It is "defconfig", not "suitable-config-for-debian-9" :-)].

Best regards,
Pavel

+++ b/arch/arm/configs/shmobile_defconfig
@@ -226,3 +226,4 @@ CONFIG_NLS_ISO8859_1=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
# CONFIG_ARM_UNWIND is not set
+CONFIG_DEBUG_FS=y
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


There is no CIP IRC weekly meeting today

masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
 

Hi,

As was discussed last week, there is no CIP IRC weekly meeting today.

Best regards,
--
M. Kudo


Re: [linux-cip:linux-4.19.y-cip 7/17] drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for 'drm_atomic_get_old_private_obj_state'

Pavel Machek
 

Hi!

I have received a warning message mail from Kernel test robot. I have investigated this issue and found there were lots of warnings with architecture by following the steps mentioned in this mail.

Then I investigated this particular issue and found that issue is caused by bad commit done by me while backporting. The below backport commit has
extra functions from patch1(0001-drm-Add-drm_atomic_get_old-new_private_obj_state.patch), but the corresponding header is missing.

cip commit: cacc2a81b9872aa8830353110b1252021f124ae8
upstream commit: 1b27fbdde1df172dba604855c45078d741f8c858

I have attached 3 patches, that looks like fixes the issue mentioned by kernel robot.

How do we proceed here?
drop cip commit: cacc2a81b9872aa8830353110b1252021f124ae8 and apply the 3 patches to fix this issue?
No, let's not revert anything.

This is trivial fix for first issue, make it into patch:

diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h
index c0b48e25a620..9042fdae9211 100644
--- a/include/drm/drm_atomic.h
+++ b/include/drm/drm_atomic.h
@@ -402,6 +402,12 @@ void drm_atomic_private_obj_fini(struct drm_private_obj *obj);
struct drm_private_state * __must_check
drm_atomic_get_private_obj_state(struct drm_atomic_state *state,
struct drm_private_obj *obj);
+struct drm_private_state *
+drm_atomic_get_old_private_obj_state(struct drm_atomic_state *state,
+ struct drm_private_obj *obj);
+struct drm_private_state *
+drm_atomic_get_new_private_obj_state(struct drm_atomic_state *state,
+ struct drm_private_obj *obj);

struct drm_connector *
drm_atomic_get_old_connector_for_encoder(struct drm_atomic_state
*state,

And this is somehow strange / non-trivial thingie. Make it into second
patch, and maybe try to explain what is going on there.

Best regards,
Pavel

@@ -656,6 +662,7 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->connectors[__i].ptr && \
((connector) = (__state)->connectors[__i].ptr, \
+ (void)(connector) /* Only to avoid unused-but-set-variable warning */, \
(old_connector_state) = (__state)->connectors[__i].old_state, \
(new_connector_state) = (__state)->connectors[__i].new_state, 1))

@@ -677,6 +684,7 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->connectors[__i].ptr && \
((connector) = (__state)->connectors[__i].ptr, \
+ (void)(connector) /* Only to avoid unused-but-set-variable warning */, \
(old_connector_state) = (__state)->connectors[__i].old_state, 1))

/**
@@ -697,7 +705,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->connectors[__i].ptr && \
((connector) = (__state)->connectors[__i].ptr, \
- (new_connector_state) = (__state)->connectors[__i].new_state, 1))
+ (void)(connector) /* Only to avoid unused-but-set-variable warning */, \
+ (new_connector_state) = (__state)->connectors[__i].new_state, \
+ (void)(new_connector_state) /* Only to avoid unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_crtc_in_state - iterate over all CRTCs in an atomic update
@@ -717,7 +727,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->crtcs[__i].ptr && \
((crtc) = (__state)->crtcs[__i].ptr, \
+ (void)(crtc) /* Only to avoid unused-but-set-variable warning */, \
(old_crtc_state) = (__state)->crtcs[__i].old_state, \
+ (void)(old_crtc_state) /* Only to avoid unused-but-set-variable warning */, \
(new_crtc_state) = (__state)->crtcs[__i].new_state, 1))

/**
@@ -756,7 +768,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->crtcs[__i].ptr && \
((crtc) = (__state)->crtcs[__i].ptr, \
- (new_crtc_state) = (__state)->crtcs[__i].new_state, 1))
+ (void)(crtc) /* Only to avoid unused-but-set-variable warning */, \
+ (new_crtc_state) = (__state)->crtcs[__i].new_state, \
+ (void)(new_crtc_state) /* Only to avoid unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_plane_in_state - iterate over all planes in an atomic update
@@ -776,6 +790,7 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->planes[__i].ptr && \
((plane) = (__state)->planes[__i].ptr, \
+ (void)(plane) /* Only to avoid unused-but-set-variable warning */, \
(old_plane_state) = (__state)->planes[__i].old_state,\
(new_plane_state) = (__state)->planes[__i].new_state, 1))

@@ -836,7 +851,9 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p);
(__i)++) \
for_each_if ((__state)->planes[__i].ptr && \
((plane) = (__state)->planes[__i].ptr, \
- (new_plane_state) = (__state)->planes[__i].new_state, 1))
+ (void)(plane) /* Only to avoid unused-but-set-variable warning */, \
+ (new_plane_state) = (__state)->planes[__i].new_state, \
+ (void)(new_plane_state) /* Only to avoid unused-but-set-variable warning */, 1))

/**
* for_each_oldnew_private_obj_in_state - iterate over all private objects in an atomic update



--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Re: [linux-cip:linux-4.19.y-cip 7/17] drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for 'drm_atomic_get_old_private_obj_state'

Pavel Machek
 

Hi!

I have received a warning message mail from Kernel test robot. I have investigated this issue and found there were lots of warnings with architecture by following the steps mentioned in this mail.

Then I investigated this particular issue and found that issue is caused by bad commit done by me while backporting. The below backport commit has
extra functions from patch1(0001-drm-Add-drm_atomic_get_old-new_private_obj_state.patch), but the corresponding header is missing.

cip commit: cacc2a81b9872aa8830353110b1252021f124ae8
upstream commit: 1b27fbdde1df172dba604855c45078d741f8c858

I have attached 3 patches, that looks like fixes the issue mentioned by kernel robot.

How do we proceed here?
drop cip commit: cacc2a81b9872aa8830353110b1252021f124ae8 and apply the 3 patches to fix this issue?
First I want to make sure: we are talking about commit
60b4667275b60d92c760d48df95f5b80bbcfde6e? Because I don't see
cacc2a81b9872aa8830353110b1252021f124ae8 around.

Best regards,
Pavel

commit 60b4667275b60d92c760d48df95f5b80bbcfde6e
Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Date: Wed Jul 22 17:34:39 2020 +0100

drm: Add drm_atomic_get_(old|new)_connector_for_encoder() helpers

commit 1b27fbdde1df172dba604855c45078d741f8c858 upstream.

Add functions to the atomic core to retrieve the old and new
connectors associated with an encoder in a drm_atomic_state. This
is useful for encoders and bridges that need to access the
connector, for instance for the drm_display_info.


--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Re: [PATCH] drm: of: Fix linking when CONFIG_OF is not set

Pavel Machek
 

Hi!

I assume this patch is for 4.19-cip?

commit 528d06d41b80a4acb2a9efd33bfc87495147f75e upstream.

The new helper drm_of_lvds_get_dual_link_pixel_order() introduced in
commit 6529007522de has a fallback stub when CONFIG_OF is not set, but
the stub is declared in drm_of.h without a static inline. This causes
multiple definitions of the function to be linked when the CONFIG_OF
option isn't set. Fix it by making the stub static inline.
So this is pretty obvious, and I'll likely apply it.

Best regards,
Pavel


diff --git a/include/drm/drm_of.h b/include/drm/drm_of.h
index 8ec7ca6d2369..b9b093add92e 100644
--- a/include/drm/drm_of.h
+++ b/include/drm/drm_of.h
@@ -92,8 +92,9 @@ static inline int drm_of_find_panel_or_bridge(const struct device_node *np,
return -EINVAL;
}

-int drm_of_lvds_get_dual_link_pixel_order(const struct device_node *port1,
- const struct device_node *port2)
+static inline int
+drm_of_lvds_get_dual_link_pixel_order(const struct device_node *port1,
+ const struct device_node *port2)
{
return -EINVAL;
}
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


[PATCH] drm: of: Fix linking when CONFIG_OF is not set

Biju Das <biju.das.jz@...>
 

From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>

commit 528d06d41b80a4acb2a9efd33bfc87495147f75e upstream.

The new helper drm_of_lvds_get_dual_link_pixel_order() introduced in
commit 6529007522de has a fallback stub when CONFIG_OF is not set, but
the stub is declared in drm_of.h without a static inline. This causes
multiple definitions of the function to be linked when the CONFIG_OF
option isn't set. Fix it by making the stub static inline.

Fixes: 6529007522de ("drm: of: Add drm_of_lvds_get_dual_link_pixel_order")
Reported-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Reviewed-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20191219103703.8547-1-laurent.pinchart+renesas@ideasonboard.com
Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
Reported-by: kernel test robot <lkp@intel.com>
---
include/drm/drm_of.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/include/drm/drm_of.h b/include/drm/drm_of.h
index 8ec7ca6d2369..b9b093add92e 100644
--- a/include/drm/drm_of.h
+++ b/include/drm/drm_of.h
@@ -92,8 +92,9 @@ static inline int drm_of_find_panel_or_bridge(const struct device_node *np,
return -EINVAL;
}

-int drm_of_lvds_get_dual_link_pixel_order(const struct device_node *port1,
- const struct device_node *port2)
+static inline int
+drm_of_lvds_get_dual_link_pixel_order(const struct device_node *port1,
+ const struct device_node *port2)
{
return -EINVAL;
}
--
2.17.1


Re: [linux-cip:linux-4.19.y-cip 7/17] drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for 'drm_atomic_get_old_private_obj_state'

Biju Das <biju.das.jz@...>
 

Hi All,

I have received a warning message mail from Kernel test robot. I have investigated this issue and found there were lots of warnings with architecture by following the steps mentioned in this mail.

Then I investigated this particular issue and found that issue is caused by bad commit done by me while backporting. The below backport commit has
extra functions from patch1(0001-drm-Add-drm_atomic_get_old-new_private_obj_state.patch), but the corresponding header is missing.

cip commit: cacc2a81b9872aa8830353110b1252021f124ae8
upstream commit: 1b27fbdde1df172dba604855c45078d741f8c858

I have attached 3 patches, that looks like fixes the issue mentioned by kernel robot.

How do we proceed here?
drop cip commit: cacc2a81b9872aa8830353110b1252021f124ae8 and apply the 3 patches to fix this issue?

Please share your views.

Regards,
Biju

-----Original Message-----
From: kernel test robot <lkp@intel.com>
Sent: 09 August 2020 15:13
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: kbuild-all@lists.01.org; Pavel Machek <pavel@denx.de>; Daniel Vetter
<daniel@ffwll.ch>; Sean Paul <seanpaul@chromium.org>; Biju Das
<biju.das.jz@bp.renesas.com>
Subject: [linux-cip:linux-4.19.y-cip 7/17]
drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype for
'drm_atomic_get_old_private_obj_state'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git linux-
4.19.y-cip
head: 72750517bc5f1718ce3cb3fa75d4cadc05d27eee
commit: 60b4667275b60d92c760d48df95f5b80bbcfde6e [7/17] drm: Add
drm_atomic_get_(old|new)_connector_for_encoder() helpers
config: riscv-randconfig-r034-20200809 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-
tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 60b4667275b60d92c760d48df95f5b80bbcfde6e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0
make.cross ARCH=riscv

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

drivers/gpu/drm/drm_atomic.c:1264:1: warning: no previous prototype
for 'drm_atomic_get_old_private_obj_state' [-Wmissing-prototypes]
1264 | drm_atomic_get_old_private_obj_state(struct drm_atomic_state
*state,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/drm_atomic.c:1286:1: warning: no previous prototype
for 'drm_atomic_get_new_private_obj_state' [-Wmissing-prototypes]
1286 | drm_atomic_get_new_private_obj_state(struct drm_atomic_state
*state,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/drm_atomic.c: In function 'drm_atomic_print_state':
drivers/gpu/drm/drm_atomic.c:2184:24: warning: variable 'connector' set
but not used [-Wunused-but-set-variable]
2184 | struct drm_connector *connector;
| ^~~~~~~~~
drivers/gpu/drm/drm_atomic.c:2182:19: warning: variable 'crtc' set but not
used [-Wunused-but-set-variable]
2182 | struct drm_crtc *crtc;
| ^~~~
drivers/gpu/drm/drm_atomic.c:2180:20: warning: variable 'plane' set but
not used [-Wunused-but-set-variable]
2180 | struct drm_plane *plane;
| ^~~~~
drivers/gpu/drm/drm_atomic.c: In function 'complete_signaling':
drivers/gpu/drm/drm_atomic.c:2624:19: warning: variable 'crtc' set but not
used [-Wunused-but-set-variable]
2624 | struct drm_crtc *crtc;
| ^~~~

vim +/drm_atomic_get_old_private_obj_state +1264
drivers/gpu/drm/drm_atomic.c

1254
1255/**
1256 * drm_atomic_get_old_private_obj_state
1257 * @state: global atomic state object
1258 * @obj: private_obj to grab
1259 *
1260 * This function returns the old private object state for the given
private_obj,
1261 * or NULL if the private_obj is not part of the global atomic state.
1262 */
1263struct drm_private_state *
1264drm_atomic_get_old_private_obj_state(struct drm_atomic_state
*state,
1265 struct drm_private_obj *obj)
1266{
1267int i;
1268
1269for (i = 0; i < state->num_private_objs; i++)
1270if (obj == state->private_objs[i].ptr)
1271return state->private_objs[i].old_state;
1272
1273return NULL;
1274}
1275EXPORT_SYMBOL(drm_atomic_get_old_private_obj_state);
1276
1277/**
1278 * drm_atomic_get_new_private_obj_state
1279 * @state: global atomic state object
1280 * @obj: private_obj to grab
1281 *
1282 * This function returns the new private object state for the given
private_obj,
1283 * or NULL if the private_obj is not part of the global atomic state.
1284 */
1285struct drm_private_state *
1286drm_atomic_get_new_private_obj_state(struct drm_atomic_state
*state,
1287 struct drm_private_obj *obj)
1288{
1289int i;
1290
1291for (i = 0; i < state->num_private_objs; i++)
1292if (obj == state->private_objs[i].ptr)
1293return state->private_objs[i].new_state;
1294
1295return NULL;
1296}
1297EXPORT_SYMBOL(drm_atomic_get_new_private_obj_state);
1298

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

Renesas Electronics Europe GmbH, Geschaeftsfuehrer/President: Carsten Jauch, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany, Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647


[ANNOUNCE] Release v4.19.138-cip32 and v4.4.231-cip48-rebase

Nobuhiro Iwamatsu
 

Hi,

CIP kernel team has released Linux kernel v4.19.138-cip32 and v4.4.231-cip48-rebase.
The linux-4.19.y-cip tree has been updated base version from v4.19.134 to v4.19.138,
and the linux-4.4.y-cip tree has been updated base version from
v4.4.230 to v4.4.231.
And In linux-4.4.y-cip, a patch for adding the updatitng DU and touch panel functions for RZ/G1 has been added.

You can get this release via the git tree at:

v4.19.138-cip32:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.19.y-cip
commit hash:
87e30ad380b2da89b8fb27e61a38c467a628b102
added commits:
CIP: Bump version suffix to -cip32 after merge from stable
drm: of: Fix double-free bug

v4.4.231-cip48-rebase:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.4.y-cip
commit hash:
7d8ea507fea1b69557994f3dc0d96d2505af95ea
added commits:
CIP: Bump version suffix to -cip48 after merge from stable
ARM: dts: iwg22d-sodimm: Enable touchscreen
ARM: dts: iwg22d-sodimm: Enable LCD panel
ARM: shmobile: defconfig: Enable support for panels from EDT
ARM: shmobile: defconfig: Enable frame buffer console for armadillo800eva
drm: rcar-du: Use the DRM panel API
drm: rcar-du: Support panels connected directly to the DPAD outputs
drm/panel: simple: Add EDT panel support
dt-bindings: display: Add bindings for EDT panel
of: add node name compare helper functions
drm: Add an encoder and connector type enum for DPI.
serial: sh-sci: Make sure status register SCxSR is read in correct sequence

Best regards,
Nobuhiro


Re: [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config

Nobuhiro Iwamatsu
 

Hi,

-----Original Message-----
From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Quirin Gylstorff
Sent: Thursday, August 6, 2020 11:27 PM
To: cip-dev@lists.cip-project.org; sangorrin daniel(サンゴリン ダニエル □SWC◯ACT)
<daniel.sangorrin@toshiba.co.jp>; jan.kiszka@siemens.com
Subject: Re: [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config



On 8/6/20 8:46 AM, Nobuhiro Iwamatsu wrote:
Hi,

Thanks for your patch.

-----Original Message-----
From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Quirin Gylstorff
Sent: Monday, August 3, 2020 7:12 PM
To: cip-dev@lists.cip-project.org; sangorrin daniel(サンゴリン ダニエル □SWC◯ACT)
<daniel.sangorrin@toshiba.co.jp>; jan.kiszka@siemens.com
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config

From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

If EFI_STUB is not active booting QEMU with OVMF efi will fail
with the following error message `KVM internal error. Suberror: 3`.

OVMF efi is used in isar-cip-core to demonstrate secure-boot with
a unified kernel image.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
4.19.y-cip/x86/cip_qemu_defconfig | 1 +
1 file changed, 1 insertion(+)
Please update cip_qemu.sources too.
When i try to generate the sources - all .c and asm files are no longer
part of the cip-qemu.sources. Did I miss something? Or should I try
again like the last time this happened?
Thanks for your check.
Sorry, I wanted to check if there was a fix in cip_qemu.sources.
I applied this patch.

Thanks,
Quirin
Best regards,
Nobuhiro


Re: [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config

Quirin Gylstorff
 

On 8/6/20 8:46 AM, Nobuhiro Iwamatsu wrote:
Hi,
Thanks for your patch.

-----Original Message-----
From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Quirin Gylstorff
Sent: Monday, August 3, 2020 7:12 PM
To: cip-dev@lists.cip-project.org; sangorrin daniel(サンゴリン ダニエル □SWC◯ACT)
<daniel.sangorrin@toshiba.co.jp>; jan.kiszka@siemens.com
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config

From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

If EFI_STUB is not active booting QEMU with OVMF efi will fail
with the following error message `KVM internal error. Suberror: 3`.

OVMF efi is used in isar-cip-core to demonstrate secure-boot with
a unified kernel image.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
4.19.y-cip/x86/cip_qemu_defconfig | 1 +
1 file changed, 1 insertion(+)
Please update cip_qemu.sources too.
When i try to generate the sources - all .c and asm files are no longer part of the cip-qemu.sources. Did I miss something? Or should I try again like the last time this happened?

Best regards,
Nobuhiro
Thanks,
Quirin


Re: [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config

Nobuhiro Iwamatsu
 

Hi,

Thanks for your patch.

-----Original Message-----
From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Quirin Gylstorff
Sent: Monday, August 3, 2020 7:12 PM
To: cip-dev@lists.cip-project.org; sangorrin daniel(サンゴリン ダニエル □SWC◯ACT)
<daniel.sangorrin@toshiba.co.jp>; jan.kiszka@siemens.com
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config

From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

If EFI_STUB is not active booting QEMU with OVMF efi will fail
with the following error message `KVM internal error. Suberror: 3`.

OVMF efi is used in isar-cip-core to demonstrate secure-boot with
a unified kernel image.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
4.19.y-cip/x86/cip_qemu_defconfig | 1 +
1 file changed, 1 insertion(+)
Please update cip_qemu.sources too.

Best regards,
Nobuhiro


Re: CIP IRC weekly meeting today

Akihiro Suzuki
 

Hi Kudo-san,

Sorry, I will be absent today's IRC meeting because I've got a plan already today.
SW Updates WG don't have any updates this week.

Best regards,
Suzuki

-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of masashi.kudo@cybertrust.co.jp
Sent: Thursday, August 6, 2020 8:51 AM
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP IRC weekly meeting today

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting from the first week of Apr. according to TSC meeting*
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=8&day=6&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

USWest USEast UK DE TW JP
02:00 05:00 10:00 11:00 17:00 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/07/cip.2020-07-30-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - iwamatsu
2. Post LTP results to KernelCI - patersonc

* Kernel maintenance updates
* Kernel testing
* Software update
* CIP Security
* AOB

The meeting will take 30 min, although it can be extended to an hour if it makes sense and those involved in the topics can stay. Otherwise, the topic will be taken offline or in the next meeting.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.


CIP IRC weekly meeting today

masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
 

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting from the first week of Apr. according to TSC meeting*
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=8&day=6&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

USWest USEast UK DE TW JP
02:00 05:00 10:00 11:00 17:00 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://irclogs.baserock.org/meetings/cip/2020/07/cip.2020-07-30-09.00.log.html

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - iwamatsu
2. Post LTP results to KernelCI - patersonc

* Kernel maintenance updates
* Kernel testing
* Software update
* CIP Security
* AOB

The meeting will take 30 min, although it can be extended to an hour if it makes sense and those involved in the topics can stay. Otherwise, the topic will be taken offline or in the next meeting.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.

1941 - 1960 of 7061