public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>
Cc: netdev@vger•kernel.org, kvalo@codeaurora•org,
	linux-wireless@vger•kernel.org, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org, igor.mitsyanko.os@quantenna•com,
	dlebed@quantenna•com, smaksimenko@quantenna•com,
	smatyukevich@quantenna•com, btherthala@quantenna•com,
	hwang@quantenna•com, krath@quantenna•com, avinashp@quantenna•com
Subject: Re: linux-next: build failure after merge of the wireless-drivers-next tree
Date: Fri, 16 Jun 2017 04:25:19 +1000	[thread overview]
Message-ID: <20170616042519.40f63561@canb.auug.org.au> (raw)
In-Reply-To: <20170615.120808.1402317729827497353.davem@davemloft.net>

Hi Dave,

On Thu, 15 Jun 2017 12:08:08 -0400 (EDT) David Miller <davem@davemloft•net> wrote:
>
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Date: Tue, 13 Jun 2017 12:00:24 +1000
> 
> > On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:  
> >>
> >> After merging the wireless-drivers-next tree, today's linux-next build
> >> (x86_64 allmodconfig) failed like this:
> >> 
> >> drivers/net/wireless/quantenna/qtnfmac/core.c: In function 'qtnf_core_net_attach':
> >> drivers/net/wireless/quantenna/qtnfmac/core.c:319:5: error: 'struct net_device' has no member named 'destructor'
> >>   dev->destructor = free_netdev;
> >>      ^
> >> 
> >> Caused by commit
> >> 
> >>   98f44cb0655c ("qtnfmac: introduce new FullMAC driver for Quantenna chipsets")  
> > 
> > This commit is now in the net-next tree ...
> >   
> >> interacting with commit
> >> 
> >>   cf124db566e6 ("net: Fix inconsistent teardown and release of private netdev state.")
> >> 
> >> from the net tree.
> >> 
> >> I applied this merge fix patch for today.  
> > 
> > So this merge fix patch is needed when the net and net-next trees are merged.  
> 
> This is now all resolved, thanks!

Thanks for letting me know.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-06-15 18:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08  2:27 linux-next: build failure after merge of the wireless-drivers-next tree Stephen Rothwell
2017-06-08  2:43 ` Igor Mitsyanko
2017-06-08  2:57   ` Stephen Rothwell
2017-06-08 12:07     ` Kalle Valo
2017-06-08 12:47       ` Stephen Rothwell
2017-06-13  2:00 ` Stephen Rothwell
2017-06-15 16:08   ` David Miller
2017-06-15 18:25     ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-08  8:49 Stephen Rothwell
2020-12-08  8:54 ` Kalle Valo
2018-08-03  8:29 Stephen Rothwell
2018-08-03  9:09 ` Kalle Valo
2018-08-03  9:11 ` Stanislaw Gruszka
2018-08-03  9:21   ` Stanislaw Gruszka
2016-07-19  6:08 Stephen Rothwell
2016-07-19  6:30 ` Kalle Valo
2016-07-19  6:51   ` Rafał Miłecki
2016-07-19  7:09     ` Kalle Valo
     [not found]       ` <871t2qw1cz.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2016-07-19  7:11         ` Rafał Miłecki
2016-07-19 14:08           ` Kalle Valo
2016-07-19 18:39             ` Brian Norris
2016-07-19 23:36               ` Stephen Rothwell
2016-07-20 18:31               ` Kalle Valo
2016-02-18 23:10 Stephen Rothwell
2016-02-19  8:08 ` Kalle Valo
2015-08-07  3:16 Stephen Rothwell
2015-08-09  8:41 ` Kalle Valo
2015-07-22  0:32 Stephen Rothwell
2015-07-22  6:07 ` Kalle Valo
2015-07-27  5:41 ` Kalle Valo
2015-07-27  6:04   ` Stephen Rothwell
2015-05-27  2:03 Stephen Rothwell
2015-05-27  9:08 ` Arend van Spriel
2015-05-28  1:38   ` Stephen Rothwell
2015-01-27  8:03 Stephen Rothwell
2015-01-27  8:13 ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170616042519.40f63561@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=avinashp@quantenna$(echo .)com \
    --cc=btherthala@quantenna$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dlebed@quantenna$(echo .)com \
    --cc=hwang@quantenna$(echo .)com \
    --cc=igor.mitsyanko.os@quantenna$(echo .)com \
    --cc=krath@quantenna$(echo .)com \
    --cc=kvalo@codeaurora$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-wireless@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=smaksimenko@quantenna$(echo .)com \
    --cc=smatyukevich@quantenna$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox