All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Re: cassini compwb fixup
Date: Mon, 06 Feb 2006 08:40:06 +0000	[thread overview]
Message-ID: <43E70B66.9060408@bfs.de> (raw)

hi list,
this is a problem that only the author can resolve.
perhaps this is used in some embedded system or so.
I would advise to fix the obvious problem before removing
since this may break an otherwise working driver.

re,
  walter


Alexey Dobriyan wrote:
>> drivers/net/cassini.c: fix undefined variable
>>
>> We had a discussion about %L vs %ll in cassini but we agreed that you
>> will change %L into %ll so perhaps that went an other way.
> 
> Warnings were fixed since then. I wonder if driver is used with
> USE_TX_COMPWB undefined. If not #ifdefs should be removed. Also we may
> stop printing after status and not print 0 at all.
> 
> --- a/drivers/net/cassini.c
> +++ b/drivers/net/cassini.c
> @@ -1946,10 +1946,11 @@ static inline void cas_tx_ringN(struct c
>  static void cas_tx(struct net_device *dev, struct cas *cp,
>  		   u32 status)
>  {
>          int limit, ring;
> +	u64 compwb = 0;
>  #ifdef USE_TX_COMPWB
> -	u64 compwb = le64_to_cpu(cp->init_block->tx_compwb);
> +	compwb = le64_to_cpu(cp->init_block->tx_compwb);
>  #endif
>  	if (netif_msg_intr(cp))
>  		printk(KERN_DEBUG "%s: tx interrupt, status: 0x%x, %llx\n",
>  			cp->dev->name, status, (unsigned long long)compwb);
> 
> 
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

                 reply	other threads:[~2006-02-06  8:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=43E70B66.9060408@bfs.de \
    --to=wharms@bfs.de \
    --cc=kernel-janitors@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.