All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Werner Sembach <wse@tuxedocomputers.com>
Cc: stable@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Christoffer Sandberg <cs@tuxedo.de>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1.y] ALSA: hda/realtek: Fix headset mic on TUXEDO Gemini 17 Gen3
Date: Sat, 9 Nov 2024 15:58:00 +0100	[thread overview]
Message-ID: <2024110938-graffiti-equity-2c07@gregkh> (raw)
In-Reply-To: <b768433e-c146-46af-a077-3e2631a4c292@tuxedocomputers.com>

On Wed, Nov 06, 2024 at 11:51:16AM +0100, Werner Sembach wrote:
> Hi
> 
> Am 06.11.24 um 11:42 schrieb Greg KH:
> > On Wed, Nov 06, 2024 at 10:49:04AM +0100, Werner Sembach wrote:
> > > From: Christoffer Sandberg <cs@tuxedo.de>
> > > 
> > > Quirk is needed to enable headset microphone on missing pin 0x19.
> > > 
> > > Signed-off-by: Christoffer Sandberg <cs@tuxedo.de>
> > > Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> > > Cc: <stable@vger.kernel.org>
> > > Link: https://patch.msgid.link/20241029151653.80726-1-wse@tuxedocomputers.com
> > > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > > ---
> > >   sound/pci/hda/patch_realtek.c | 1 +
> > >   1 file changed, 1 insertion(+)
> > What is the git commit id of this in Linus's tree?
> 
> 0b04fbe886b4274c8e5855011233aaa69fec6e75
> 
> Is there a specific format/tag to add it to the commit? something like
> "Mainline-commit: <hash>". Didn't find anything in the documentation.

anywhere a normal 'git cherry-pick -x' would put it is good.

thanks,

greg k-h

      reply	other threads:[~2024-11-09 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241106021124.182205-1-sashal>
2024-11-06  9:49 ` [PATCH 6.1.y] ALSA: hda/realtek: Fix headset mic on TUXEDO Gemini 17 Gen3 Werner Sembach
2024-11-06 10:42   ` Greg KH
2024-11-06 10:51     ` Werner Sembach
2024-11-09 14:58       ` Greg KH [this message]

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=2024110938-graffiti-equity-2c07@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cs@tuxedo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=wse@tuxedocomputers.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.