From: Joe Perches <joe@perches.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Raymond Yau <superquad.vortex2@gmail.com>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [alsa-devel] [PATCH v2 2/2] ALSA: au88x0: pr_* replaced with dev_*
Date: Sat, 11 Oct 2014 11:22:59 -0700 [thread overview]
Message-ID: <1413051779.22149.8.camel@joe-AO725> (raw)
In-Reply-To: <CADVatmPiWEm9wBENVVytUqCOV_Yv9HojmHYJGDAmyGpwhcCU8A@mail.gmail.com>
On Sat, 2014-10-11 at 23:40 +0530, Sudip Mukherjee wrote:
> now in this case what will you suggest - shutdown and done both
> terminated by \n or some thing like : "shutdown process started" and then
> "shutdown done"....
I think it doesn't matter one way or another as
it's only useful when there's a hang in the init
or shutdown.
It is better though to have complete messages
terminated with newlines so that it is not possible
for other threads to confusingly interleave output.
next prev parent reply other threads:[~2014-10-11 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 8:36 [PATCH v2 1/2] ALSA: au88x0: added reference of vortex_t Sudip Mukherjee
2014-10-10 8:36 ` [PATCH v2 2/2] ALSA: au88x0: pr_* replaced with dev_* Sudip Mukherjee
[not found] ` <CAN8ccibSw_85wdnxbNSKfjXQ-7Lg3C6_5fhKQJJi5xMi8pMabA@mail.gmail.com>
2014-10-11 9:09 ` [alsa-devel] " Sudip Mukherjee
2014-10-11 10:48 ` Joe Perches
2014-10-11 11:33 ` Sudip Mukherjee
2014-10-11 15:32 ` Joe Perches
[not found] ` <CADVatmPiWEm9wBENVVytUqCOV_Yv9HojmHYJGDAmyGpwhcCU8A@mail.gmail.com>
2014-10-11 18:22 ` Joe Perches [this message]
2014-10-11 18:25 ` Sudip Mukherjee
[not found] ` <CAN8cciZXLfWC-vsYq0r64Uw6D0t2z8LFVcF_i31OQg5BO7+uZQ@mail.gmail.com>
2014-10-16 13:45 ` Takashi Iwai
2014-10-17 3:32 ` Sudip Mukherjee
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=1413051779.22149.8.camel@joe-AO725 \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sudipm.mukherjee@gmail.com \
--cc=superquad.vortex2@gmail.com \
--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