From: arvind Yadav <arvind.yadav.cs@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>, linuxppc-dev@lists.ozlabs.org
Cc: zajec5@gmail.com, leoli@freescale.com, qiang.zhao@freescale.com,
viresh.kumar@linaro.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, scottwood@freescale.com,
akpm@linux-foundation.org, linux@roeck-us.net
Subject: Re: [v5.1] ucc_fast: Fix to avoid IS_ERR_VALUE abuses and dead code on 64bit systems.
Date: Fri, 5 Aug 2016 14:18:32 +0530 [thread overview]
Message-ID: <57A452E0.10904@gmail.com> (raw)
In-Reply-To: <2376517.GXv6XVOdDd@wuerfel>
On Friday 05 August 2016 02:01 AM, Arnd Bergmann wrote:
> On Thursday, August 4, 2016 10:22:43 PM CEST Arvind Yadav wrote:
>> index df8ea79..ada9070 100644
>> --- a/include/soc/fsl/qe/ucc_fast.h
>> +++ b/include/soc/fsl/qe/ucc_fast.h
>> @@ -165,10 +165,12 @@ struct ucc_fast_private {
>> int stopped_tx; /* Whether channel has been stopped for Tx
>> (STOP_TX, etc.) */
>> int stopped_rx; /* Whether channel has been stopped for Rx */
>> - u32 ucc_fast_tx_virtual_fifo_base_offset;/* pointer to base of Tx
>> - virtual fifo */
>> - u32 ucc_fast_rx_virtual_fifo_base_offset;/* pointer to base of Rx
>> - virtual fifo */
>> + unsigned long ucc_fast_tx_virtual_fifo_base_offset;/* pointer to base of
>> + * Tx virtual fifo
>> + */
>> + unsigned long ucc_fast_rx_virtual_fifo_base_offset;/* pointer to base of
>> + * Rx virtual fifo
>> + */
>> #ifdef STATISTICS
>> u32 tx_frames; /* Transmitted frames counter. */
>> u32 rx_frames; /* Received frames counter (only frames
>>
> This change seems ok, but what about the other u32 variables in ucc_geth.c
> that get checked for IS_ERR_VALUE?
>
> Arnd
> I have send separate patch for ucc_geth ans ucc_slow.
> -Arvind
next prev parent reply other threads:[~2016-08-05 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 16:52 [v5.1] ucc_fast: Fix to avoid IS_ERR_VALUE abuses and dead code on 64bit systems Arvind Yadav
2016-08-04 20:31 ` Arnd Bergmann
2016-08-05 8:48 ` arvind Yadav [this message]
2016-08-05 13:04 ` David Laight
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=57A452E0.10904@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=leoli@freescale.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=qiang.zhao@freescale.com \
--cc=scottwood@freescale.com \
--cc=viresh.kumar@linaro.org \
--cc=zajec5@gmail.com \
/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 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).