|
Super long-term kernel support
Hi CIP kernel team,
I have a question regarding the super long-term kernel support: can
other commercial or non-commercial projects make use of such kernel
versions like "linux-4.19.y-cip", i.e., use
Hi CIP kernel team,
I have a question regarding the super long-term kernel support: can
other commercial or non-commercial projects make use of such kernel
versions like "linux-4.19.y-cip", i.e., use
|
By
Andreas Weißel <andreas.weissel@...>
·
#4530
·
|
|
BRONZE BV Inquiry
Hi Sir/Madam,
Glad to hear that you are on the market for valves, we specialize in this field for 13 years with the strength of FLANGED BRONZE BUTTERFLY VALVES with good quality and pretty
Hi Sir/Madam,
Glad to hear that you are on the market for valves, we specialize in this field for 13 years with the strength of FLANGED BRONZE BUTTERFLY VALVES with good quality and pretty
|
By
WORLDS VALVE <tjwdsv@...>
·
#4529
·
|
|
Re: [backport 4.4] mac80211: Fix TKIP replay protection immediately after key setup
The security tracker shows a lot of fixes missing from 4.4.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House,
The security tracker shows a lot of fixes missing from 4.4.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House,
|
By
Ben Hutchings <ben.hutchings@...>
·
#4528
·
|
|
Re: [backport 4.4] mac80211: Fix TKIP replay protection immediately after key setup
That's what I would do.
This reference is wrong; the upstream commit is
6f601265215a421f425ba3a4850a35861d024643. Also the usual format for
this reference has "upstream." after the commit
That's what I would do.
This reference is wrong; the upstream commit is
6f601265215a421f425ba3a4850a35861d024643. Also the usual format for
this reference has "upstream." after the commit
|
By
Ben Hutchings <ben.hutchings@...>
·
#4527
·
|
|
Re: realtime on de0-nano bisection
Hi Pavel,
Just repeat the test case name 5 times in the gitlab-ci file.
E.g. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/791b84001ce05a9a26117a0c2de0e7250b343960
Regards, Chris
Hi Pavel,
Just repeat the test case name 5 times in the gitlab-ci file.
E.g. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/791b84001ce05a9a26117a0c2de0e7250b343960
Regards, Chris
|
By
Chris Paterson
·
#4526
·
|
|
Re: Backporting "net: ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup"
I also had a go at this before catching up on cip-dev and finding you
had also done so. So I've compared this with my version.
I haven't done real testing yet either.
This leaves the ret variable
I also had a go at this before catching up on cip-dev and finding you
had also done so. So I've compared this with my version.
I haven't done real testing yet either.
This leaves the ret variable
|
By
Ben Hutchings <ben.hutchings@...>
·
#4525
·
|
|
Re: realtime on de0-nano bisection
Hi!
That's my job, I guess. I asked for bisect and got bisect
(thanks!). And yes, I have to agree:
In the
Hi!
That's my job, I guess. I asked for bisect and got bisect
(thanks!). And yes, I have to agree:
In the
|
By
Pavel Machek
·
#4524
·
|
|
Re: Linux-cip: Kselftest plans
[...]
Some self-tests will fail on older kernel versions due to missing
features or bugs that might not be practically fixable. Test cases can
report "skip" rather than "fail" for missing features,
[...]
Some self-tests will fail on older kernel versions due to missing
features or bugs that might not be practically fixable. Test cases can
report "skip" rather than "fail" for missing features,
|
By
Ben Hutchings <ben.hutchings@...>
·
#4523
·
|
|
Re: realtime on de0-nano bisection
[...]
[...]
When bisection finds a commit touching code that you're not even
building, the answer should not be "don't ask me why" but "this is not
a reproducible bug".
Ben.
--
Ben Hutchings,
[...]
[...]
When bisection finds a commit touching code that you're not even
building, the answer should not be "don't ask me why" but "this is not
a reproducible bug".
Ben.
--
Ben Hutchings,
|
By
Ben Hutchings <ben.hutchings@...>
·
#4522
·
|
|
Re: realtime on de0-nano bisection
Hi Pavel,
Last 'good' patch is: 2089f853a8c3 ("drm/i915: disable tracing on -RT")
The first 'bad' path is: c82fe0af5e58 ("drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE")
Don't ask me
Hi Pavel,
Last 'good' patch is: 2089f853a8c3 ("drm/i915: disable tracing on -RT")
The first 'bad' path is: c82fe0af5e58 ("drm/i915: skip DRM_I915_LOW_LEVEL_TRACEPOINTS with NOTRACE")
Don't ask me
|
By
Chris Paterson
·
#4521
·
|
|
Re: realtime on de0-nano bisection
Hi Pavel,
FYI, if it's only one build/test config you're interested in, you can save time/compute by modifying the .gitlab-ci.yml file in your tree.
See an example
Hi Pavel,
FYI, if it's only one build/test config you're interested in, you can save time/compute by modifying the .gitlab-ci.yml file in your tree.
See an example
|
By
Chris Paterson
·
#4520
·
|
|
Re: realtime on de0-nano bisection
Hello Pavel,
What Kernel config are you using?
Do you mean 4.19.106-rt44 Is bad?
I'll get bisecting.
Regards, Chris
Hello Pavel,
What Kernel config are you using?
Do you mean 4.19.106-rt44 Is bad?
I'll get bisecting.
Regards, Chris
|
By
Chris Paterson
·
#4519
·
|
|
realtime on de0-nano bisection
Hi!
I'm fighting with realtime on de0-nano, and I could use some
help... locating the bad commit. I don't seem to know enough about
test infrastructure to be effective. I pushed a tree I'm interested
Hi!
I'm fighting with realtime on de0-nano, and I could use some
help... locating the bad commit. I don't seem to know enough about
test infrastructure to be effective. I pushed a tree I'm interested
|
By
Pavel Machek
·
#4518
·
|
|
Re: CIP IRC weekly meeting today
Hi, Iwamatsu-san,
Thanks for your updates! Also thanks for your offer about #AI-2!
We will discuss this in the IRC.
Best regards,
--
M. Kudo
Hi, Iwamatsu-san,
Thanks for your updates! Also thanks for your offer about #AI-2!
We will discuss this in the IRC.
Best regards,
--
M. Kudo
|
By
masashi.kudo@...
·
#4517
·
|
|
Re: CIP IRC weekly meeting today
Hi Kudo-san,
I can't attend IRC meetings today.
Hi Kudo-san,
I can't attend IRC meetings today.
|
By
Nobuhiro Iwamatsu
·
#4516
·
|
|
[ANNOUNCE] Release v4.19.109-cip22 and v4.4.216-cip43
Hi all,
CIP kernel team has released Linux kernel v4.19.109-cip22 and v4.4.216-cip43.
Release was delayed due to test confirmation delay, sorry.
The linux-4.19.y-cip tree has been updated base
Hi all,
CIP kernel team has released Linux kernel v4.19.109-cip22 and v4.4.216-cip43.
Release was delayed due to test confirmation delay, sorry.
The linux-4.19.y-cip tree has been updated base
|
By
Nobuhiro Iwamatsu
·
#4515
·
|
|
Re: Please check health for renesas board on LAVA
Hi,
By
Nobuhiro Iwamatsu
·
#4514
·
|
|
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
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
|
By
masashi.kudo@...
·
#4513
·
|
|
Re: Please check health for renesas board on LAVA
I'm not sure if we'll cope with the latency though...
I'm not sure if we'll cope with the latency though...
|
By
Chris Paterson
·
#4512
·
|
|
Re: Please check health for renesas board on LAVA
Hi!
I'd suggest a moon rather than the moon. Europa could work, just to be
sure :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
Hi!
I'd suggest a moon rather than the moon. Europa could work, just to be
sure :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
|
By
Pavel Machek
·
#4511
·
|