|
Re: Codethink report weeks 14 - 17
Hi,
Documentation updated - see below
Agustín Benito Bethencourt <agustin.benito@...> writes:
This has now mostly been completed - the text has been updated
#181 has been opened - and
Hi,
Documentation updated - see below
Agustín Benito Bethencourt <agustin.benito@...> writes:
This has now mostly been completed - the text has been updated
#181 has been opened - and
|
By
Robert Marshall <robert.marshall@...>
·
#1094
·
|
|
Re: Linux 4.4.126-cip22
I'll send out the patches to Greg since they are also missing in v4.4 stable as soon I have build tested this here. takes a while...
I'll send out the patches to Greg since they are also missing in v4.4 stable as soon I have build tested this here. takes a while...
|
By
Daniel Wagner <wagi@...>
·
#1093
·
|
|
Re: Linux 4.4.126-cip22
Uwe was faster. I think you should add these two patches to your tree:
82a3f87f6e80 ("serial: mctrl_gpio: Add missing module license")
f71a2e0a282 ("serial: mctrl_gpio: export mctrl_gpio_disable_ms
Uwe was faster. I think you should add these two patches to your tree:
82a3f87f6e80 ("serial: mctrl_gpio: Add missing module license")
f71a2e0a282 ("serial: mctrl_gpio: export mctrl_gpio_disable_ms
|
By
Daniel Wagner <wagi@...>
·
#1092
·
|
|
Re: Linux 4.4.126-cip22
I guess those two symbols are just missing the export. Patch in the works.
I guess those two symbols are just missing the export. Patch in the works.
|
By
Daniel Wagner <wagi@...>
·
#1091
·
|
|
Re: Linux 4.4.126-cip22
Hi Ben,
While working on the cip-rt spin I got following error from our ci build server:
Errors:
-------
all annotations:
~~~~~~~~~~~~~~~~
ERROR: "mctrl_gpio_disable_ms"
Hi Ben,
While working on the cip-rt spin I got following error from our ci build server:
Errors:
-------
all annotations:
~~~~~~~~~~~~~~~~
ERROR: "mctrl_gpio_disable_ms"
|
By
Daniel Wagner <wagi@...>
·
#1090
·
|
|
Codethink report weeks 14 - 17
Hi,
several interesting accomplishments these past weeks. Here is the report about
Codethink's activities at CIP.
## CIP kernel maintenance
* New CIP kernel released: 4.4.126-cip22
* Kernel
Hi,
several interesting accomplishments these past weeks. Here is the report about
Codethink's activities at CIP.
## CIP kernel maintenance
* New CIP kernel released: 4.4.126-cip22
* Kernel
|
By
Agustín Benito Bethencourt <agustin.benito@...>
·
#1089
·
|
|
Re: Reviewing 4.4 stable updates
Oh, that's strange. Agustin and I each tried sending it and neither of
us saw it come back from the list.
[...]
[...]
Yes, 4.4.129 is released and there will be a 4.4.130 review some time
soon.
Oh, that's strange. Agustin and I each tried sending it and neither of
us saw it come back from the list.
[...]
[...]
Yes, 4.4.129 is released and there will be a 4.4.130 review some time
soon.
|
By
Ben Hutchings <ben.hutchings@...>
·
#1088
·
|
|
Re: Reviewing 4.4 stable updates
Hi Ben,
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#1087
·
|
|
Reviewing 4.4 stable updates
I intended to bounce the review messages for 4.4.128 to this list so
everyone could see them, but this seems to be blocked by some mail
filter.
Instead I've saved them to an mbox file which is
I intended to bounce the review messages for 4.4.128 to this list so
everyone could see them, but this seems to be blocked by some mail
filter.
Instead I've saved them to an mbox file which is
|
By
Ben Hutchings <ben.hutchings@...>
·
#1086
·
|
|
Re: Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC
Freedom of choice, for the comfortability and usability reasons.
Zoran
_______
<agustin.benito@...> wrote:
Freedom of choice, for the comfortability and usability reasons.
Zoran
_______
<agustin.benito@...> wrote:
|
By
Zoran
·
#1085
·
|
|
Re: Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC
Hi,
And the arguments for such reconsideration in your opinion are.... ?
wrote:
--
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd
Hi,
And the arguments for such reconsideration in your opinion are.... ?
wrote:
--
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd
|
By
Agustín Benito Bethencourt <agustin.benito@...>
·
#1084
·
|
|
Re: Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC
TSC should reconsider (at least to duplicate).
Zoran
_______
<agustin.benito@...> wrote:
TSC should reconsider (at least to duplicate).
Zoran
_______
<agustin.benito@...> wrote:
|
By
Zoran
·
#1083
·
|
|
[Git][cip-project/cip-testing/board-at-desk-single-dev][master] 2 commits: Renesas changes for a working health check
Robert Marshall pushed to branch masterat cip-project / cip-testing / board-at-desk-single-devCommits:
e5146230
by Robert Marshallat 2018-04-20T15:30:03ZRenesas changes for a working health
Robert Marshall pushed to branch masterat cip-project / cip-testing / board-at-desk-single-devCommits:
e5146230
by Robert Marshallat 2018-04-20T15:30:03ZRenesas changes for a working health
|
By
Agustin Benito Bethencourt
·
#1081
·
|
|
CIP related article in LWN.net
Hi,
https://lwn.net/Articles/749530/
as you can see there are several comments. Ben H. and myself has answered a
couple.
Yoshi, you might want to read mine since I named you.
Best Regards
--
Hi,
https://lwn.net/Articles/749530/
as you can see there are several comments. Ben H. and myself has answered a
couple.
Yoshi, you might want to read mine since I named you.
Best Regards
--
|
By
Agustín Benito Bethencourt <agustin.benito@...>
·
#1080
·
|
|
Re: ARM64 and Debian LTS
Debian prefers but doesn't absolutely require server type systems.
None of the existing ARM (32-bit) or MIPS systems used as Debian
buildds or porterboxes appear to be designed as servers.
Ben.
--
Debian prefers but doesn't absolutely require server type systems.
None of the existing ARM (32-bit) or MIPS systems used as Debian
buildds or porterboxes appear to be designed as servers.
Ben.
--
|
By
Ben Hutchings <ben.hutchings@...>
·
#1079
·
|
|
Re: Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC
Hi Zoran
We use gitlab based on a TSC (Technical Steering Committee) decision.
--
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd
Hi Zoran
We use gitlab based on a TSC (Technical Steering Committee) decision.
--
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd
|
By
Agustín Benito Bethencourt <agustin.benito@...>
·
#1078
·
|
|
Re: Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC
Hi,
This is no longer the repo location.
I confirm this is the new URL. Please act accordingly.
Best Regards
--
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd
Hi,
This is no longer the repo location.
I confirm this is the new URL. Please act accordingly.
Best Regards
--
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd
|
By
Agustín Benito Bethencourt <agustin.benito@...>
·
#1077
·
|
|
Re: Important: planned movement of the cip-kernel repo on Gitlab: Thursday 19th April 10:00 UTC
Here, I would like to propose the same to be replicated on GitHub.
Personally, I do like much more GitHub... But this is me and my
wishes, only! ;-)
Zoran
<agustin.benito@...> wrote:
Here, I would like to propose the same to be replicated on GitHub.
Personally, I do like much more GitHub... But this is me and my
wishes, only! ;-)
Zoran
<agustin.benito@...> wrote:
|
By
Zoran
·
#1076
·
|
|
Minutes: Re: cip-dev IRC meeting agenda: week 16
Hi,
please find the minutes of the cip-dev meeting
https://irclogs.baserock.org/cip/%23cip.
2018-04-19.log.html#t2018-04-19T09:00:48
Best Regards
--
Agustín Benito Bethencourt
Principal
Hi,
please find the minutes of the cip-dev meeting
https://irclogs.baserock.org/cip/%23cip.
2018-04-19.log.html#t2018-04-19T09:00:48
Best Regards
--
Agustín Benito Bethencourt
Principal
|
By
Agustín Benito Bethencourt <agustin.benito@...>
·
#1075
·
|
|
[PATCH 6/6] i2c: rcar: init new messages in irq
From: Wolfram Sang <wsa+renesas@...>
Setting up new messages was done in process context while handling a
message was in interrupt context. Because of the HW design, this IP core
is
From: Wolfram Sang <wsa+renesas@...>
Setting up new messages was done in process context while handling a
message was in interrupt context. Because of the HW design, this IP core
is
|
By
Fabrizio Castro <fabrizio.castro@...>
·
#1074
·
|