Daily JIRA Digest


Kalowsky, Daniel <daniel.kalowsky@...>
 

-----Original Message-----
From: donotreply(a)jenkins.zephyrproject.org
[mailto:donotreply(a)jenkins.zephyrproject.org]
Sent: Wednesday, April 6, 2016 9:47 AM
To: devel(a)lists.zephyrproject.org
Subject: [devel] Daily JIRA Digest

NEW JIRA items within last 24 hours: 2
B [ZEP-184] (P 2) QMSI 'CONFIG_RTC_IRQ_PRI' undeclared.
B [ZEP-183] (P 3) [regression]PINMUX_NUM_PINS is missing in
arch/x86/soc/quark_se/soc.h
The fact that I'm needing a decoder key/ring for these emails is not useful.

What does the B before each line mean?

Not convinced the priority is needed in these emails. It really does nothing to add to the title except create some bizarre string encryption.


UPDATED JIRA items within last 24 hours: 2
B [ZEP-75] (P 1) REOPENED Zephyr compiler fails with error about executing
cc1
B [ZEP-7] (P 3) REOPENED Arduino 101 GPIO_INT_LEVEL not working as
expected

CLOSED JIRA items within last 24 hours: 3
B [ZEP-174] (Fixed) Hello_world app build fail with error:
'PINMUX_BASE_ADDR' undeclared when
PINMUX_DEV,PINMUX_DEV_QUARK_MCU were enabled
B [ZEP-161] (Won't Do) Nothing output when run hello_world app with x86
SDK for quark platforms
B [ZEP-151] (Fixed) QMSI AON_TIMER_IRQ and AON_TIMER_IRQ_PRI have
not been configured in quark_se_devboard
Why is the closed status being inserted here? Anyone interested in that can and should go look at the JIRA.


RESOLVED JIRA items within last 24 hours: 0


Perez Hernandez, Javier B <javier.b.perez.hernandez@...>
 

Dan,

On Thu, 2016-04-07 at 00:34 +0000, Kalowsky, Daniel wrote:

-----Original Message-----
From: donotreply(a)jenkins.zephyrproject.org
[mailto:donotreply(a)jenkins.zephyrproject.org]
Sent: Wednesday, April 6, 2016 9:47 AM
To: devel(a)lists.zephyrproject.org
Subject: [devel] Daily JIRA Digest

NEW JIRA items within last 24 hours: 2
  B [ZEP-184] (P 2) QMSI 'CONFIG_RTC_IRQ_PRI' undeclared.
  B [ZEP-183] (P 3) [regression]PINMUX_NUM_PINS is missing in
arch/x86/soc/quark_se/soc.h
The fact that I'm needing a decoder key/ring for these emails is not
useful.  

What does the B before each line mean?

Not convinced the priority is needed in these emails.  It really does
nothing to add to the title except create some bizarre string
encryption.
It is the first letter of the issue type (Bug, Requirement, Story).

I will probably changed to something like:
Bug:
  [ZEP-] ...
Story
  ..




UPDATED JIRA items within last 24 hours: 2
  B [ZEP-75]  (P 1) REOPENED Zephyr compiler fails with error about
executing
cc1
  B [ZEP-7]   (P 3) REOPENED Arduino 101 GPIO_INT_LEVEL not working
as
expected

CLOSED JIRA items within last 24 hours: 3
  B [ZEP-174] (Fixed) Hello_world app build fail with  error:
'PINMUX_BASE_ADDR' undeclared when
PINMUX_DEV,PINMUX_DEV_QUARK_MCU were enabled
  B [ZEP-161] (Won't Do) Nothing output when run hello_world app
with x86
SDK for quark platforms
  B [ZEP-151] (Fixed) QMSI AON_TIMER_IRQ and AON_TIMER_IRQ_PRI have
not been configured in quark_se_devboard
Why is the closed status being inserted here?   Anyone interested in
that can and should go look at the JIRA.



RESOLVED JIRA items within last 24 hours: 0


Kalowsky, Daniel <daniel.kalowsky@...>
 

-----Original Message-----
From: Perez Hernandez, Javier B
Sent: Thursday, April 7, 2016 8:35 AM
To: Kalowsky, Daniel <daniel.kalowsky(a)intel.com>;
devel(a)lists.zephyrproject.org
Subject: Re: [devel] Re: Daily JIRA Digest

Dan,

On Thu, 2016-04-07 at 00:34 +0000, Kalowsky, Daniel wrote:

-----Original Message-----
From: donotreply(a)jenkins.zephyrproject.org
[mailto:donotreply(a)jenkins.zephyrproject.org]
Sent: Wednesday, April 6, 2016 9:47 AM
To: devel(a)lists.zephyrproject.org
Subject: [devel] Daily JIRA Digest

NEW JIRA items within last 24 hours: 2
  B [ZEP-184] (P 2) QMSI 'CONFIG_RTC_IRQ_PRI' undeclared.
  B [ZEP-183] (P 3) [regression]PINMUX_NUM_PINS is missing in
arch/x86/soc/quark_se/soc.h
The fact that I'm needing a decoder key/ring for these emails is not
useful.

What does the B before each line mean?

Not convinced the priority is needed in these emails.  It really does
nothing to add to the title except create some bizarre string
encryption.
It is the first letter of the issue type (Bug, Requirement, Story).

I will probably changed to something like:
Bug:
  [ZEP-] ...
Story
Please don't. Again, you're just creating an extremely difficult line of text to read. Anyone who wants that data can find it in the JIRA entry itself. The point of this email to make people aware of issues being filed that they really might not have been on the notification list for so that they may add themselves to the watch list.

The point is NOT to reproduce all of a JIRA entry in email.


  ..




UPDATED JIRA items within last 24 hours: 2
  B [ZEP-75]  (P 1) REOPENED Zephyr compiler fails with error about
executing
cc1
  B [ZEP-7]   (P 3) REOPENED Arduino 101 GPIO_INT_LEVEL not working
as
expected

CLOSED JIRA items within last 24 hours: 3
  B [ZEP-174] (Fixed) Hello_world app build fail with  error:
'PINMUX_BASE_ADDR' undeclared when
PINMUX_DEV,PINMUX_DEV_QUARK_MCU were enabled
  B [ZEP-161] (Won't Do) Nothing output when run hello_world app
with x86
SDK for quark platforms
  B [ZEP-151] (Fixed) QMSI AON_TIMER_IRQ and AON_TIMER_IRQ_PRI
have
not been configured in quark_se_devboard
Why is the closed status being inserted here?   Anyone interested in
that can and should go look at the JIRA.



RESOLVED JIRA items within last 24 hours: 0


donotreply@...
 

NEW JIRA items within last 24 hours: 7
[ZEP-2078] tests/kernel/stackprot/testcase.ini - failing for arc/a101 and arc/qc1000
https://jira.zephyrproject.org/browse/ZEP-2078

[ZEP-2079] tests/crypto/test_ccm_mode - failing for mintvaslley(quark_d2000)
https://jira.zephyrproject.org/browse/ZEP-2079

[ZEP-2077] [net][bt]Set wrong IID for neighbor
https://jira.zephyrproject.org/browse/ZEP-2077

[ZEP-2075] Arduino 101 filesystem fails test
https://jira.zephyrproject.org/browse/ZEP-2075

[ZEP-2082] filtering pattern in scripts/support/dfuutil.sh doesn't work for arduino_101
https://jira.zephyrproject.org/browse/ZEP-2082

[ZEP-2081] New Zephyr-defined types missing API documentation
https://jira.zephyrproject.org/browse/ZEP-2081

[ZEP-2083] Bluetooth data types missing API documentation
https://jira.zephyrproject.org/browse/ZEP-2083


UPDATED JIRA items within last 24 hours: 25
[ZEP-2068] Need Tasks to Be Tracked in QRC too
https://jira.zephyrproject.org/browse/ZEP-2068

[ZEP-834] Thread requirements in RFC1122
https://jira.zephyrproject.org/browse/ZEP-834

[ZEP-835] Thread requirements in RFC2460
https://jira.zephyrproject.org/browse/ZEP-835

[ZEP-836] Thread requirements in RFC4291
https://jira.zephyrproject.org/browse/ZEP-836

[ZEP-837] Thread requirements in RFC4443
https://jira.zephyrproject.org/browse/ZEP-837

[ZEP-838] Thread requirements in RFC4944
https://jira.zephyrproject.org/browse/ZEP-838

[ZEP-948] Revisit the timeslicing algorithm
https://jira.zephyrproject.org/browse/ZEP-948

[ZEP-2053] Update tinycrypt to v.0.2.6 in recent releases
https://jira.zephyrproject.org/browse/ZEP-2053

[ZEP-1946] Time to Next Event
https://jira.zephyrproject.org/browse/ZEP-1946

[ZEP-1818] Add tickless kernel support in cortex_m_systick timer
https://jira.zephyrproject.org/browse/ZEP-1818

[ZEP-1816] Add tickless kernel support in LOAPIC timer
https://jira.zephyrproject.org/browse/ZEP-1816

[ZEP-1817] Add tickless kernel support in ARCV2 timer
https://jira.zephyrproject.org/browse/ZEP-1817

[ZEP-1812] Add tickless kernel support in HPET timer
https://jira.zephyrproject.org/browse/ZEP-1812

[ZEP-1821] Update PM apps to use mili/micro seconds instead of ticks
https://jira.zephyrproject.org/browse/ZEP-1821

[ZEP-2069] samples:net:dhcpv4_client: runs failed on frdm k64f board
https://jira.zephyrproject.org/browse/ZEP-2069

[ZEP-2057] crash in tests/net/rpl on qemu_x86 causing intermittent sanitycheck failure
https://jira.zephyrproject.org/browse/ZEP-2057

[ZEP-1868] [IPv6 TAHI] Section 1: RFC 2460 - IPv6 Specification
https://jira.zephyrproject.org/browse/ZEP-1868

[ZEP-1874] [IPv6 TAHI] Section 3: RFC 4862 - IPv6 Stateless Address Autoconfiguration
https://jira.zephyrproject.org/browse/ZEP-1874

[ZEP-1875] [IPv6 TAHI] Section 2: RFC 4861 - Neighbor Discovery for IPv6
https://jira.zephyrproject.org/browse/ZEP-1875

[ZEP-1869] [IPv6 TAHI]Section 4: RFC 1981 - Path MTU Discovery for IPv6
https://jira.zephyrproject.org/browse/ZEP-1869

[ZEP-1870] [IPv6 TAHI]Section 5: RFC 4443 - ICMPv6
https://jira.zephyrproject.org/browse/ZEP-1870

[ZEP-2015] the http_client sample app runs failed on FRDM K64F board
https://jira.zephyrproject.org/browse/ZEP-2015

[ZEP-1939] DataReady triggers failed to stop on BMI160 when both Accel/Gyro is enabled
https://jira.zephyrproject.org/browse/ZEP-1939

[ZEP-2014] Defaul samples/subsys/shell/shell fails to build on QEMU RISCv32 / NIOS2
https://jira.zephyrproject.org/browse/ZEP-2014

[ZEP-2064] RFC: Making net_shell command handlers reusable
https://jira.zephyrproject.org/browse/ZEP-2064


CLOSED JIRA items within last 24 hours: 2
[ZEP-2011] (Done) Retrieve RPL node information through CoAP requests
https://jira.zephyrproject.org/browse/ZEP-2011

[ZEP-1984] (Fixed) net_nbuf_append(), net_nbuf_append_bytes() have data integrity problems
https://jira.zephyrproject.org/browse/ZEP-1984


RESOLVED JIRA items within last 24 hours: 0