public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
	David Miller <davem@davemloft•net>,
	"Michael S. Tsirkin" <mst@redhat•com>
Subject: Re: linux-next: Tree for Dec 10 (ethernet/8390/8390p.c)
Date: Wed, 11 Dec 2019 09:34:49 +1100	[thread overview]
Message-ID: <20191211093449.0932cef4@canb.auug.org.au> (raw)
In-Reply-To: <ce89aa80-558c-1ccb-afbe-0af6bc4f3e19@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

Hi Randy,

On Mon, 9 Dec 2019 23:13:34 -0800 Randy Dunlap <rdunlap@infradead•org> wrote:
>
> On 12/9/19 7:02 PM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20191209:
> >   
> 
> on i386:
> 
> ../drivers/net/ethernet/8390/8390p.c:44:6: error: conflicting types for ‘eip_tx_timeout’
>  void eip_tx_timeout(struct net_device *dev, unsigned int txqueue)
>       ^~~~~~~~~~~~~~
> In file included from ../drivers/net/ethernet/8390/lib8390.c:75:0,
>                  from ../drivers/net/ethernet/8390/8390p.c:12:
> ../drivers/net/ethernet/8390/8390.h:53:6: note: previous declaration of ‘eip_tx_timeout’ was here
>  void eip_tx_timeout(struct net_device *dev);
>       ^~~~~~~~~~~~~~

Looks like this has been fixed for today (in the vhost tree).
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2019-12-10 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  3:02 linux-next: Tree for Dec 10 Stephen Rothwell
2019-12-10  7:13 ` linux-next: Tree for Dec 10 (ethernet/8390/8390p.c) Randy Dunlap
2019-12-10  8:24   ` David Miller
2019-12-10 22:34   ` Stephen Rothwell [this message]

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=20191211093449.0932cef4@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mst@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rdunlap@infradead$(echo .)org \
    /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