Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Emil Bartczak
On Mon, Dec 05, 2016 at 11:15:59PM +0100, Alexandre Belloni wrote: > On 05/12/2016 at 23:03:52 +0100, Emil Bartczak wrote : > > > > > > > #define MCP795_WRITE 0x12 > > > > #define MCP795_UNLOCK 0x14 > > > > #define MCP795_IDWRITE 0x32 > > > > @@ -39,6 +39,7 @@ > > > > > > > > #define

Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Emil Bartczak
On Mon, Dec 05, 2016 at 11:15:59PM +0100, Alexandre Belloni wrote: > On 05/12/2016 at 23:03:52 +0100, Emil Bartczak wrote : > > > > > > > #define MCP795_WRITE 0x12 > > > > #define MCP795_UNLOCK 0x14 > > > > #define MCP795_IDWRITE 0x32 > > > > @@ -39,6 +39,7 @@ > > > > > > > > #define

Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Alexandre Belloni
On 05/12/2016 at 23:03:52 +0100, Emil Bartczak wrote : > > > > > #define MCP795_WRITE 0x12 > > > #define MCP795_UNLOCK0x14 > > > #define MCP795_IDWRITE 0x32 > > > @@ -39,6 +39,7 @@ > > > > > > #define MCP795_ST_BIT0x80 > > > #define MCP795_24_BIT0x40 > > > +#define

Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Alexandre Belloni
On 05/12/2016 at 23:03:52 +0100, Emil Bartczak wrote : > > > > > #define MCP795_WRITE 0x12 > > > #define MCP795_UNLOCK0x14 > > > #define MCP795_IDWRITE 0x32 > > > @@ -39,6 +39,7 @@ > > > > > > #define MCP795_ST_BIT0x80 > > > #define MCP795_24_BIT0x40 > > > +#define

Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Emil Bartczak
Hi, On Mon, Dec 05, 2016 at 04:09:59PM +0100, Alexandre Belloni wrote: > Hi, > > On 05/12/2016 at 14:11:50 +0100, Emil Bartczak wrote : > > The 10 month register was always set to value 0 in the RTC hardware. > > Due to the bug month November or December became February. > > All your patches

Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Emil Bartczak
Hi, On Mon, Dec 05, 2016 at 04:09:59PM +0100, Alexandre Belloni wrote: > Hi, > > On 05/12/2016 at 14:11:50 +0100, Emil Bartczak wrote : > > The 10 month register was always set to value 0 in the RTC hardware. > > Due to the bug month November or December became February. > > All your patches

Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Alexandre Belloni
Hi, On 05/12/2016 at 14:11:50 +0100, Emil Bartczak wrote : > The 10 month register was always set to value 0 in the RTC hardware. > Due to the bug month November or December became February. All your patches are missing your SoB, see Developer's Certificate of Origin 1.1 in

Re: [PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Alexandre Belloni
Hi, On 05/12/2016 at 14:11:50 +0100, Emil Bartczak wrote : > The 10 month register was always set to value 0 in the RTC hardware. > Due to the bug month November or December became February. All your patches are missing your SoB, see Developer's Certificate of Origin 1.1 in

[PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Emil Bartczak
The 10 month register was always set to value 0 in the RTC hardware. Due to the bug month November or December became February. --- drivers/rtc/rtc-mcp795.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/drivers/rtc/rtc-mcp795.c b/drivers/rtc/rtc-mcp795.c index

[PATCH 1/4] rtc: mcp795: fix invalid month setting.

2016-12-05 Thread Emil Bartczak
The 10 month register was always set to value 0 in the RTC hardware. Due to the bug month November or December became February. --- drivers/rtc/rtc-mcp795.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/drivers/rtc/rtc-mcp795.c b/drivers/rtc/rtc-mcp795.c index