From: Takashi Iwai <tiwai@suse.de>
To: Joe Perches <joe@perches.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
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, 03 Nov 2014 16:18:58 +0100 [thread overview]
Message-ID: <s5hoaso1fdp.wl-tiwai@suse.de> (raw)
In-Reply-To: <1415027288.17743.16.camel@perches.com>
At Mon, 03 Nov 2014 07:08:08 -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?
All look OK at a quick glance. There was a recent change to make
card->dev mandatory, so it's there from the very beginning.
> ftrace exists and is generic.
>
> Several of these seem to be function tracing
> style uses and should just be deleted instead.
True. Further cleanup patches appreciated.
thanks,
Takashi
next prev parent reply other threads:[~2014-11-03 15:19 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 [this message]
2014-11-03 16:52 ` Sudip Mukherjee
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=s5hoaso1fdp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sudipm.mukherjee@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