All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: Patch subject line (was: Re: [PATCH] asoc: bfin: use dev_err to print error log instead of dev_dbg)
Date: Thu, 21 Jun 2012 16:22:44 +0100	[thread overview]
Message-ID: <20120621152244.GW4037@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FE334CA.7090205@canonical.com>


[-- Attachment #1.1: Type: text/plain, Size: 482 bytes --]

On Thu, Jun 21, 2012 at 04:50:50PM +0200, David Henningsson wrote:

> While we're at it, how about switching to the a/b/c style used by
> several other subsystems?

Looking at the git logs that's *really* unusual.

> I personally think "alsa/hda/realtek" looks much prettier than the
> shoutier "ALSA: HDA: Realtek:" thing we have today.

I have to say I really don't like this, especially the lowercasing of
everything.  It doesn't read like normal text, it reads like a filename.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-06-21 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 17:51 [PATCH] asoc: bfin: use dev_err to print error log instead of dev_dbg Scott Jiang
2012-06-21 10:08 ` Mark Brown
2012-06-21 10:29   ` Scott Jiang
2012-06-21 10:47     ` Mark Brown
2012-06-21 14:50       ` Patch subject line (was: Re: [PATCH] asoc: bfin: use dev_err to print error log instead of dev_dbg) David Henningsson
2012-06-21 15:22         ` Mark Brown [this message]
2012-06-21 15:31           ` Takashi Iwai
2012-06-21 15:39             ` Mark Brown

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=20120621152244.GW4037@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.