From: Geert Uytterhoeven <geert@linux-m68k.org> To: Tony Breeds <tony@bakeyournoodle.com> Cc: Randy Dunlap <randy.dunlap@oracle.com>, Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, Jeff Garzik <jgarzik@redhat.com>, David Miller <davem@davemloft.net>, netdev@vger.kernel.org, Linux/m68k <linux-m68k@vger.kernel.org> Subject: Re: linux-next: Tree for May 14 Date: Fri, 16 May 2008 09:12:51 +0200 (CEST) [thread overview] Message-ID: <Pine.LNX.4.64.0805160911400.22059@anakin> (raw) In-Reply-To: <20080516021009.GS20457@bakeyournoodle.com> On Fri, 16 May 2008, Tony Breeds wrote: > On Thu, May 15, 2008 at 09:17:15AM +0200, Geert Uytterhoeven wrote: > > Technically, it could also happen on PPC (APUS), but all APUS support got > > removed a few months ago. > > So maybe CONFIG_ZORRO is more appropriate? > > Well as it turns out it can happen in a few other plcaes (the same error > is visible on sh aswell: > http://kisskb.ellerman.id.au/kisskb/buildresult/27769/ ) > > Below is a new fix. Thoughts?. Looks OK to me! > --- a/drivers/net/lib8390.c > +++ b/drivers/net/lib8390.c > @@ -553,6 +553,9 @@ static void __ei_poll(struct net_device *dev) > static void ei_tx_err(struct net_device *dev) > { > unsigned long e8390_base = dev->base_addr; > + /* ei_local is used on some platforms via the EI_SHIFT macro */ > + struct ei_device *ei_local __maybe_unused = > + (struct ei_device *) netdev_priv(dev); ^^^^^^^^^^^^^^^^^^^^ But please don't reintroduce the casts. netdev_priv() returns a void *. > unsigned char txsr = ei_inb_p(e8390_base+EN0_TSR); > unsigned char tx_was_aborted = txsr & (ENTSR_ABT+ENTSR_FU); > > @@ -815,6 +818,9 @@ static void ei_rx_overrun(struct net_device *dev) > { > unsigned long e8390_base = dev->base_addr; > unsigned char was_txing, must_resend = 0; > + /* ei_local is used on some platforms via the EI_SHIFT macro */ > + struct ei_device *ei_local __maybe_unused = > + (struct ei_device *) netdev_priv(dev); ^^^^^^^^^^^^^^^^^^^^ Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next prev parent reply other threads:[~2008-05-16 7:12 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-14 7:01 Stephen Rothwell 2008-05-14 20:38 ` Geert Uytterhoeven 2008-05-14 20:50 ` Randy Dunlap 2008-05-14 21:04 ` Tony Breeds 2008-05-15 1:05 ` Tony Breeds 2008-05-15 7:17 ` Geert Uytterhoeven 2008-05-15 7:23 ` Stephen Rothwell 2008-05-16 2:10 ` Tony Breeds 2008-05-16 7:12 ` Geert Uytterhoeven [this message] 2008-05-19 5:03 ` [PATCH v3] Fix various 8390 builds Tony Breeds 2009-05-14 6:41 linux-next: Tree for May 14 Stephen Rothwell 2009-05-14 13:17 ` Nico -telmich- Schottelius 2010-05-14 6:14 Stephen Rothwell 2012-05-14 10:03 Stephen Rothwell 2013-05-14 4:17 Stephen Rothwell 2014-05-14 8:26 Stephen Rothwell 2015-05-14 8:25 Stephen Rothwell 2018-05-14 7:20 Stephen Rothwell 2018-05-14 7:26 ` Andy Shevchenko 2018-05-14 12:40 ` Stephen Rothwell 2018-05-14 17:14 ` Andy Shevchenko 2018-05-14 21:54 ` Stephen Rothwell 2019-05-14 4:35 Stephen Rothwell 2020-05-14 11:07 Stephen Rothwell 2021-05-14 5:40 Stephen Rothwell
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=Pine.LNX.4.64.0805160911400.22059@anakin \ --to=geert@linux-m68k.org \ --cc=davem@davemloft.net \ --cc=jgarzik@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-m68k@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=randy.dunlap@oracle.com \ --cc=sfr@canb.auug.org.au \ --cc=tony@bakeyournoodle.com \ --subject='Re: linux-next: Tree for May 14' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).