On Wed, Dec 6, 2017 at 9:51 PM, Rob Herring wrote:
> On Tue, Dec 5, 2017 at 4:48 PM, Stephen Rothwell
> wrote:
> These 2 aren't in -next and seem to have been missed:
>
> arm: dts: qcom: fix missing #phy-cells for apq8064
Apparently this is a subsect of 3191b5b332f8 ("ARM: dts: qcom-apq8064: Fi
On Tue, Dec 5, 2017 at 4:48 PM, Stephen Rothwell wrote:
> Hi Rob,
>
> On Wed, 15 Nov 2017 17:12:00 -0600 Rob Herring wrote:
>>
>> On Wed, Nov 15, 2017 at 4:42 PM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > On Thu, 9 Nov 2017 08:37:00 -0600 Rob Herring wrote:
>> >>
>> >> On Thu, Nov 9, 2
Hi Rob,
On Wed, 15 Nov 2017 17:12:00 -0600 Rob Herring wrote:
>
> On Wed, Nov 15, 2017 at 4:42 PM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > On Thu, 9 Nov 2017 08:37:00 -0600 Rob Herring wrote:
> >>
> >> On Thu, Nov 9, 2017 at 1:42 AM, Linus Walleij
> >> wrote:
> >> > On Thu, Nov 9,
Hi Rob,
On Wed, 15 Nov 2017 17:12:00 -0600 Rob Herring wrote:
>
> On Wed, Nov 15, 2017 at 4:42 PM, Stephen Rothwell
> wrote:
> >
> > So these (many) warnings are now in Linus' tree :-(
> >
> > Please do something about them.
>
> Patches are in flight. I got all the low hanging fruit that are
On Wed, Nov 15, 2017 at 4:42 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 9 Nov 2017 08:37:00 -0600 Rob Herring wrote:
>>
>> On Thu, Nov 9, 2017 at 1:42 AM, Linus Walleij
>> wrote:
>> > On Thu, Nov 9, 2017 at 4:51 AM, Stephen Rothwell
>> > wrote:
>> >> On Fri, 3 Nov 2017 16:37:24 +1100 S
Hi all,
On Thu, 9 Nov 2017 08:37:00 -0600 Rob Herring wrote:
>
> On Thu, Nov 9, 2017 at 1:42 AM, Linus Walleij
> wrote:
> > On Thu, Nov 9, 2017 at 4:51 AM, Stephen Rothwell
> > wrote:
> >> On Fri, 3 Nov 2017 16:37:24 +1100 Stephen Rothwell
> >> wrote:
> >>>
> >>> After merging the gpio
On Thu, Nov 9, 2017 at 1:42 AM, Linus Walleij wrote:
> On Thu, Nov 9, 2017 at 4:51 AM, Stephen Rothwell
> wrote:
>> On Fri, 3 Nov 2017 16:37:24 +1100 Stephen Rothwell
>> wrote:
>>>
>>> After merging the gpio tree, yesterday's linux-next build (arm
>>> multi_v7_defconfig) produced these warning
On Thu, Nov 9, 2017 at 4:51 AM, Stephen Rothwell wrote:
> On Fri, 3 Nov 2017 16:37:24 +1100 Stephen Rothwell
> wrote:
>>
>> After merging the gpio tree, yesterday's linux-next build (arm
>> multi_v7_defconfig) produced these warnings:
>>
>> arch/arm/boot/dts/bcm2835-rpi-b.dtb: Warning (phys_prop
Hi Linus,
On Fri, 3 Nov 2017 16:37:24 +1100 Stephen Rothwell
wrote:
>
> After merging the gpio tree, yesterday's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
>
> arch/arm/boot/dts/bcm2835-rpi-b.dtb: Warning (phys_property): Missing
> property '#phy-cells' in node /phy o
Hi Linus,
After merging the gpio tree, yesterday's linux-next build (arm
multi_v7_defconfig) produced these warnings:
arch/arm/boot/dts/bcm2835-rpi-b.dtb: Warning (phys_property): Missing property
'#phy-cells' in node /phy or bad phandle (referred from
/soc/usb@7e98:phys[0])
arch/arm/boot/d
On Wed, Jul 23, 2014 at 10:45 AM, Stephen Rothwell
wrote:
> After merging the gpio tree, today's linux-next build (powerpc
> allyesconfig) produced these warnings:
>
> drivers/gpio/gpio-ucb1400.c: In function 'ucb1400_gpio_remove':
> drivers/gpio/gpio-ucb1400.c:92:2: warning: ignoring return val
Hi Linus,
After merging the gpio tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
drivers/gpio/gpio-ucb1400.c: In function 'ucb1400_gpio_remove':
drivers/gpio/gpio-ucb1400.c:92:2: warning: ignoring return value of
'gpiochip_remove', declared with attribute warn_unus
12 matches
Mail list logo
