All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org, woodrow.shen@canonical.com,
	1475553@bugs.launchpad.net
Subject: Re: [PATCH v1] ALSA: hda- Add headset mic pin quirk for a Dell device
Date: Fri, 24 Jul 2015 09:50:49 +0200	[thread overview]
Message-ID: <s5hd1zivvs6.wl-tiwai@suse.de> (raw)
In-Reply-To: <55B1E5FB.1080702@canonical.com>

On Fri, 24 Jul 2015 09:15:07 +0200,
David Henningsson wrote:
> 
> 
> 
> On 2015-07-24 08:54, Takashi Iwai wrote:
> > On Fri, 24 Jul 2015 06:50:42 +0200,
> > woodrow.shen@canonical.com wrote:
> >>
> >> From: Woodrow Shen <woodrow.shen@canonical.com>
> >>
> >> Fix the headset mic that will not work on Dell desktop machine.
> >> BugLink: https://bugs.launchpad.net/bugs/1475553
> >> Signed-off-by: Woodrow Shen <woodrow.shen@canonical.com>
> >
> > I have repeatedly received patches with the very same subject and with
> > the very similar content but without further explanation.  It's too
> > confusing.
> >
> > Please look through the git commit history of this file, and re-read
> > your patch.  Then, consider a more useful subject / description, and
> > resubmit the patch.
> 
> Hi Takashi,
> 
> We're doing enablement of machines and several of them need pin quirks 
> in order to have the headset mic working. Since these machines are 
> pre-release, we are not allowed to make the final name of the machine 
> public (e g, "Dell XPS 13"). For the same reason, we cannot give you 
> alsa-info either.
> 
> Given this constraint, how do you suggest we improve the subject / 
> description? Or should we wait to submit upstream until the machine has 
> been released to the market?

I don't mean to give alsa-info.sh output or such.  The problem is that
it's always with the same subject and the same text.  How do you know
it's for what and apply in which order?

At least you should try the patch looks different with each other,
describe the relationship with previous commits, etc.


thanks,

Takashi

  reply	other threads:[~2015-07-24  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  4:50 [PATCH v1] ALSA: hda- Add headset mic pin quirk for a Dell device woodrow.shen
2015-07-24  6:54 ` Takashi Iwai
2015-07-24  7:15   ` David Henningsson
2015-07-24  7:50     ` Takashi Iwai [this message]
2015-07-24  8:03       ` David Henningsson
2015-07-24  8:18         ` Takashi Iwai
2015-07-24  9:39           ` Woodrow Shen

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=s5hd1zivvs6.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=1475553@bugs.launchpad.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=woodrow.shen@canonical.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 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.