Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Wed, Mar 06, 2019 at 09:27:01PM -0800, Darren Hart wrote: > On Mon, Mar 04, 2019 at 02:37:35PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > > > include/linux/platform_data/mlxreg.h > > > > between commit: > > >

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Mon, Mar 04, 2019 at 02:37:35PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > include/linux/platform_data/mlxreg.h > > between commit: > > 9f03161a1bd8 ("platform_data/mlxreg: additions for Mellanox watchdog >

linux-next: manual merge of the drivers-x86 tree with the watchdog tree

Hi all, Today's linux-next merge of the drivers-x86 tree got a conflict in: include/linux/platform_data/mlxreg.h between commit: 9f03161a1bd8 ("platform_data/mlxreg: additions for Mellanox watchdog driver.") from the watchdog tree and commit: 9b28aa1d0eae ("platform_data/mlxreg:

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

Hi All, > On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: > > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: > > > On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > > > > On Tue, May 2, 2017 at 11:21 PM, Darren Hart > > > >

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

Hi All, > On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: > > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: > > > On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > > > > On Tue, May 2, 2017 at 11:21 PM, Darren Hart > > > > wrote: > > > > > On Tue,

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Wed, May 3, 2017 at 5:24 PM, Wim Van Sebroeck wrote: >> On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: >> > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: >> > On a side note, it appears that I tagged "watchdog: iTCO_wdt: cleanup >> > set/unset

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Wed, May 3, 2017 at 5:24 PM, Wim Van Sebroeck wrote: >> On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: >> > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: >> > On a side note, it appears that I tagged "watchdog: iTCO_wdt: cleanup >> > set/unset no_reboot_bit

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: > > On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > > > On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > > > > On Tue, May

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: > > On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > > > On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > > > > On Tue, May 02, 2017 at 12:12:17PM

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: > On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > > On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > > > On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: > > >> On Tue, May 02,

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: > On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > > On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > > > On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: > > >> On Tue, May 02, 2017 at 11:09:40AM

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > > On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: > >> On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: > >> > On Tue, May 02,

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 11:57:18PM +0300, Andy Shevchenko wrote: > On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > > On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: > >> On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: > >> > On Tue, May 02, 2017 at 02:04:03PM

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: >> On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: >> > On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > From my perspective,

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 2, 2017 at 11:21 PM, Darren Hart wrote: > On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: >> On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: >> > On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > From my perspective, the most direct

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: > On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: > > On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > >

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 12:12:17PM -0700, Guenter Roeck wrote: > On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: > > On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > >

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: > On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > > > drivers/watchdog/iTCO_wdt.c > > > > between commit: > > > >

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 11:09:40AM -0700, Darren Hart wrote: > On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > > > drivers/watchdog/iTCO_wdt.c > > > > between commit: > > > >

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > drivers/watchdog/iTCO_wdt.c > > between commit: > > 38a700fa1df9 ("watchdog: iTCO_wdt: cleanup set/unset no_reboot_bit > functions") >

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Tue, May 02, 2017 at 02:04:03PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the drivers-x86 tree got a conflict in: > > drivers/watchdog/iTCO_wdt.c > > between commit: > > 38a700fa1df9 ("watchdog: iTCO_wdt: cleanup set/unset no_reboot_bit > functions") >

linux-next: manual merge of the drivers-x86 tree with the watchdog tree

Hi all, Today's linux-next merge of the drivers-x86 tree got a conflict in: drivers/watchdog/iTCO_wdt.c between commit: 38a700fa1df9 ("watchdog: iTCO_wdt: cleanup set/unset no_reboot_bit functions") (which also appears in the drivers-x86 tree as commit f583a884afec) from the watchdog tree

linux-next: manual merge of the drivers-x86 tree with the watchdog tree

Hi all, Today's linux-next merge of the drivers-x86 tree got a conflict in: drivers/watchdog/iTCO_wdt.c between commit: 38a700fa1df9 ("watchdog: iTCO_wdt: cleanup set/unset no_reboot_bit functions") (which also appears in the drivers-x86 tree as commit f583a884afec) from the watchdog tree