From: Wolfgang Grandegger <wg@grandegger.com>
To: Abhilash K V <abhilash.kv@ti.com>
Cc: socketcan-core@lists.berlios.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Vaibhav Hiremath <hvaibhav@ti.com>
Subject: Re: [PATCH] can : TI_HECC : Unintialized variables
Date: Thu, 10 Mar 2011 18:07:32 +0100 [thread overview]
Message-ID: <4D790554.20204@grandegger.com> (raw)
In-Reply-To: <1299774087-8532-1-git-send-email-abhilash.kv@ti.com>
On 03/10/2011 05:21 PM, Abhilash K V wrote:
> 1. In ti_hecc_xmit(), "data" is not initialized, causing
> undesirable effects like setting the RTR field for every
> transmit.
Does it need to be initialized to "data = cf->can_dlc"? If yes, please
correct the message, if not ...
> 2. In ti_hecc_probe(), the spinlock priv->mbx_lock is not
> inited, causing a spinlock lockup BUG.
>
> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> Acked-by: Anant Gole <anantgole@ti.com>
> Signed-off-by: Abhilash K V <abhilash.kv@ti.com>
> ---
> drivers/net/can/ti_hecc.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/can/ti_hecc.c b/drivers/net/can/ti_hecc.c
> index 4d07f1e..73c6025 100644
> --- a/drivers/net/can/ti_hecc.c
> +++ b/drivers/net/can/ti_hecc.c
> @@ -503,6 +503,7 @@ static netdev_tx_t ti_hecc_xmit(struct sk_buff *skb, struct net_device *ndev)
> spin_unlock_irqrestore(&priv->mbx_lock, flags);
>
> /* Prepare mailbox for transmission */
> + data = cf->can_dlc;
> if (cf->can_id & CAN_RTR_FLAG) /* Remote transmission request */
> data |= HECC_CANMCF_RTR;
> data |= get_tx_head_prio(priv) << 8;
... using the following expressions looks more reasonable:
data = get_tx_head_prio(priv) << 8;
if (cf->can_id & CAN_RTR_FLAG) /* Remote transmission request */
data |= HECC_CANMCF_RTR;
Wolfgang.
prev parent reply other threads:[~2011-03-10 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 16:21 [PATCH] can : TI_HECC : Unintialized variables Abhilash K V
2011-03-10 17:07 ` Wolfgang Grandegger [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=4D790554.20204@grandegger.com \
--to=wg@grandegger.com \
--cc=abhilash.kv@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan-core@lists.berlios.de \
/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