Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1675449 > unrolled thread

[RESEND PATCH] critical patch to fix pci-tree build bot failure

Started byRyder Lee <ryder.lee@mediatek.com>
First post2017-06-27 11:30 +0200
Last post2017-06-29 00:00 +0200
Articles 6 — 4 participants

Back to article view | Back to linux.kernel


Contents

  [RESEND PATCH] critical patch to fix pci-tree build bot failure Ryder Lee <ryder.lee@mediatek.com> - 2017-06-27 11:30 +0200
    Re: [RESEND PATCH] critical patch to fix pci-tree build bot failure Bjorn Helgaas <bjorn.helgaas@gmail.com> - 2017-06-27 15:30 +0200
      Re: [RESEND PATCH] critical patch to fix pci-tree build bot failure Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-28 00:20 +0200
        Re: [RESEND PATCH] critical patch to fix pci-tree build bot failure Bjorn Helgaas <helgaas@kernel.org> - 2017-06-28 00:30 +0200
        Re: [RESEND PATCH] critical patch to fix pci-tree build bot failure Bjorn Helgaas <helgaas@kernel.org> - 2017-06-28 22:50 +0200
          Re: [RESEND PATCH] critical patch to fix pci-tree build bot failure Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-29 00:00 +0200

#1675449 — [RESEND PATCH] critical patch to fix pci-tree build bot failure

FromRyder Lee <ryder.lee@mediatek.com>
Date2017-06-27 11:30 +0200
Subject[RESEND PATCH] critical patch to fix pci-tree build bot failure
Message-ID<tWUYN-6V2-13@gated-at.bofh.it>
Hi Stephen and Andrew,

Could you help to apply this patch? Seems Bjorn didn't response it these days.

This patch(based on pci-next tree) will fix the following build bot failure:
>> On Mon, Jun 26, 2017 at 09:47:36AM +0100, Build bot for Mark Brown wrote:
>>
>> This build failure is still present in -next:
>>
>> >     arm-allmodconfig
>> > ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit 
>> > declaration of function 'pci_register_host_bridge' 
>> > [-Werror=implicit-function-declaration]
>>
>> and we're at -rc7 now.

This is because pci/host-mediatek is a seperate branch in pci-tree, but merge together without proper modifications(eg. some API changes).

Hi Bjorn,
I rewrote commit message. Please ignore my previous one, sorry for inconvenience.

Thanks a lot!

Ryder Lee (1):
  PCI: mediatek: change to use the new host bridge interface

 drivers/pci/host/pcie-mediatek.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

-- 
1.9.1

[toc] | [next] | [standalone]


#1675694

FromBjorn Helgaas <bjorn.helgaas@gmail.com>
Date2017-06-27 15:30 +0200
Message-ID<tWYJ4-14q-19@gated-at.bofh.it>
In reply to#1675449
On Tue, Jun 27, 2017 at 4:24 AM, Ryder Lee <ryder.lee@mediatek.com> wrote:
> Hi Stephen and Andrew,
>
> Could you help to apply this patch? Seems Bjorn didn't response it these days.

I'm not dead, but I was on vacation most of last week.  I'll resolve this today.

> This patch(based on pci-next tree) will fix the following build bot failure:
>>> On Mon, Jun 26, 2017 at 09:47:36AM +0100, Build bot for Mark Brown wrote:
>>>
>>> This build failure is still present in -next:
>>>
>>> >     arm-allmodconfig
>>> > ../drivers/pci/host/pcie-mediatek.c:485:8: error: implicit
>>> > declaration of function 'pci_register_host_bridge'
>>> > [-Werror=implicit-function-declaration]
>>>
>>> and we're at -rc7 now.
>
> This is because pci/host-mediatek is a seperate branch in pci-tree, but merge together without proper modifications(eg. some API changes).
>
> Hi Bjorn,
> I rewrote commit message. Please ignore my previous one, sorry for inconvenience.
>
> Thanks a lot!
>
> Ryder Lee (1):
>   PCI: mediatek: change to use the new host bridge interface
>
>  drivers/pci/host/pcie-mediatek.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
>
> --
> 1.9.1
>

[toc] | [prev] | [next] | [standalone]


#1676215

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2017-06-28 00:20 +0200
Message-ID<tX6ZY-6Ou-13@gated-at.bofh.it>
In reply to#1675694
Hi Bjorn,

On Tue, 27 Jun 2017 08:20:44 -0500 Bjorn Helgaas <bjorn.helgaas@gmail.com> wrote:
>
> On Tue, Jun 27, 2017 at 4:24 AM, Ryder Lee <ryder.lee@mediatek.com> wrote:
> > Hi Stephen and Andrew,
> >
> > Could you help to apply this patch? Seems Bjorn didn't response it these days.  
> 
> I'm not dead, but I was on vacation most of last week.  I'll resolve this today.

Should I just add this patch to linux-next today (if you don't get
around to it in the next hour or so)?

-- 
Cheers,
Stephen Rothwell

[toc] | [prev] | [next] | [standalone]


#1676222

FromBjorn Helgaas <helgaas@kernel.org>
Date2017-06-28 00:30 +0200
Message-ID<tX79E-6RF-27@gated-at.bofh.it>
In reply to#1676215
On Wed, Jun 28, 2017 at 08:10:26AM +1000, Stephen Rothwell wrote:
> Hi Bjorn,
> 
> On Tue, 27 Jun 2017 08:20:44 -0500 Bjorn Helgaas <bjorn.helgaas@gmail.com> wrote:
> >
> > On Tue, Jun 27, 2017 at 4:24 AM, Ryder Lee <ryder.lee@mediatek.com> wrote:
> > > Hi Stephen and Andrew,
> > >
> > > Could you help to apply this patch? Seems Bjorn didn't response it these days.  
> > 
> > I'm not dead, but I was on vacation most of last week.  I'll resolve this today.
> 
> Should I just add this patch to linux-next today (if you don't get
> around to it in the next hour or so)?

Sure, I think that would be OK.  Thanks!

[toc] | [prev] | [next] | [standalone]


#1677163

FromBjorn Helgaas <helgaas@kernel.org>
Date2017-06-28 22:50 +0200
Message-ID<tXs4q-2d9-29@gated-at.bofh.it>
In reply to#1676215
On Wed, Jun 28, 2017 at 08:10:26AM +1000, Stephen Rothwell wrote:
> Hi Bjorn,
> 
> On Tue, 27 Jun 2017 08:20:44 -0500 Bjorn Helgaas <bjorn.helgaas@gmail.com> wrote:
> >
> > On Tue, Jun 27, 2017 at 4:24 AM, Ryder Lee <ryder.lee@mediatek.com> wrote:
> > > Hi Stephen and Andrew,
> > >
> > > Could you help to apply this patch? Seems Bjorn didn't response it these days.  
> > 
> > I'm not dead, but I was on vacation most of last week.  I'll resolve this today.
> 
> Should I just add this patch to linux-next today (if you don't get
> around to it in the next hour or so)?

Just FYI, this should be fixed in my -next branch now, so you shouldn't
need to add the patch yourself, Stephen.

[toc] | [prev] | [next] | [standalone]


#1677209

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2017-06-29 00:00 +0200
Message-ID<tXtaa-C5-9@gated-at.bofh.it>
In reply to#1677163
Hi Bjorn,

On Wed, 28 Jun 2017 15:43:17 -0500 Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> On Wed, Jun 28, 2017 at 08:10:26AM +1000, Stephen Rothwell wrote:
> > Hi Bjorn,
> > 
> > On Tue, 27 Jun 2017 08:20:44 -0500 Bjorn Helgaas <bjorn.helgaas@gmail.com> wrote:  
> > >
> > > On Tue, Jun 27, 2017 at 4:24 AM, Ryder Lee <ryder.lee@mediatek.com> wrote:  
> > > > Hi Stephen and Andrew,
> > > >
> > > > Could you help to apply this patch? Seems Bjorn didn't response it these days.    
> > > 
> > > I'm not dead, but I was on vacation most of last week.  I'll resolve this today.  
> > 
> > Should I just add this patch to linux-next today (if you don't get
> > around to it in the next hour or so)?  
> 
> Just FYI, this should be fixed in my -next branch now, so you shouldn't
> need to add the patch yourself, Stephen.

Excellent, thanks.

-- 
Cheers,
Stephen Rothwell

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web