public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ALSA: echoaudio: add reference of struct echoaudio
Date: Mon, 3 Nov 2014 22:22:43 +0530	[thread overview]
Message-ID: <20141103165243.GA7562@sudip-PC> (raw)
In-Reply-To: <1415027288.17743.16.camel@perches.com>

On Mon, Nov 03, 2014 at 07:08:08AM -0800, Joe Perches wrote:
> On Mon, 2014-11-03 at 15:17 +0100, Takashi Iwai wrote:
> > At Mon,  3 Nov 2014 16:04:12 +0530,
> > Sudip Mukherjee wrote:
> > > 
> > > added reference of struct echoaudio to free_firmware function.
> > > this structure will be later used to get a reference of the card
> > > when converting snd_printk to dev_* in the next patch of the series.
> > > 
> > > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > 
> > Thanks, now applied both.  Though, I noticed that there is also a
> > dev_notice() usage that should be also dev_dbg().  Corrected such
> > lines in my side.
> 
> Are any of these changes going to cause a
> null pointer dereference of chip->card->dev?
should not. while converting i have checked the place from where the particular function is called, to see if chip is valid there.
if chip is valid, then chip->card->dev should be ok. card is coming from snd_card_new and chip from snd_echo_create.
> 
> ftrace exists and is generic.
> 
> Several of these seem to be function tracing
> style uses and should just be deleted instead.

function tracing style uses means?
there are some prints which are printing the function name while printing the debug message.
are those function tracing style uses??

thanks
sudip
> 
> 

  parent reply	other threads:[~2014-11-03 16:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 10:34 [PATCH v2 1/2] ALSA: echoaudio: add reference of struct echoaudio Sudip Mukherjee
2014-11-03 10:34 ` [PATCH v2 2/2] ALSA: echoaudio: remove all snd_printk Sudip Mukherjee
2014-11-03 14:17 ` [PATCH v2 1/2] ALSA: echoaudio: add reference of struct echoaudio Takashi Iwai
2014-11-03 15:08   ` Joe Perches
2014-11-03 15:18     ` Takashi Iwai
2014-11-03 16:52     ` Sudip Mukherjee [this message]
2014-11-03 17:45       ` Joe Perches

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=20141103165243.GA7562@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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