On Mon, Jan 30, 2017 at 5:28 AM, Stephen Rothwell wrote:
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
>
On Mon, Jan 30, 2017 at 5:28 AM, Stephen Rothwell wrote:
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for
On Mon, Jan 30, 2017 at 03:28:55PM +1100, Stephen Rothwell wrote:
> Hi Linus,
>
> Today's linux-next merge of the gpio tree got a conflict in:
>
> drivers/staging/greybus/gpio.c
>
> between commit:
>
> 1d3dfbd1dd34 ("staging: greybus: fix checkpatch unsigned warnings")
>
> from the
On Mon, Jan 30, 2017 at 03:28:55PM +1100, Stephen Rothwell wrote:
> Hi Linus,
>
> Today's linux-next merge of the gpio tree got a conflict in:
>
> drivers/staging/greybus/gpio.c
>
> between commit:
>
> 1d3dfbd1dd34 ("staging: greybus: fix checkpatch unsigned warnings")
>
> from the
Hi Linus,
Today's linux-next merge of the gpio tree got a conflict in:
drivers/staging/greybus/gpio.c
between commit:
1d3dfbd1dd34 ("staging: greybus: fix checkpatch unsigned warnings")
from the staging tree and commit:
2956b5d94a76 ("pinctrl / gpio: Introduce .set_config() callback
Hi Linus,
Today's linux-next merge of the gpio tree got a conflict in:
drivers/staging/greybus/gpio.c
between commit:
1d3dfbd1dd34 ("staging: greybus: fix checkpatch unsigned warnings")
from the staging tree and commit:
2956b5d94a76 ("pinctrl / gpio: Introduce .set_config() callback
6 matches
Mail list logo