All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Baole Fang <fbl718@163.com>
Cc: alsa-devel@alsa-project.org, Kailang Yang <kailang@realtek.com>,
	Jeremy Szu <jeremy.szu@canonical.com>,
	Takashi Iwai <tiwai@suse.de>,
	linux-kernel@vger.kernel.org, Elia Devito <eliadevito@gmail.com>,
	Takashi Iwai <tiwai@suse.com>,
	Werner Sembach <wse@tuxedocomputers.com>,
	Hui Wang <hui.wang@canonical.com>, Sami Loone <sami@loone.fi>,
	Cameron Berkenpas <cam@neo-zeon.de>
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Legion Y9000X 2020
Date: Wed, 5 Jan 2022 12:44:21 +0100	[thread overview]
Message-ID: <YdWElRjkZ0lybrMJ@kroah.com> (raw)
In-Reply-To: <757a4402-1067-e3c8-8ca3-43ee62047ebe@163.com>

On Wed, Jan 05, 2022 at 07:39:33PM +0800, Baole Fang wrote:
> Sorry, this is my first time to submit patch to Linux, so I'm not quite
> familiar with the convention. Since I was changing based on v5.15.12 and I
> saw others mentioning their upstream commit, I included the that commit id.

Those commits were coming from the stable backports only, they were not
done by the original author.

> Please forgive me and tell me what is supposed to be done if possible. I
> still have a lot to learn.

Please take a look at the "first kernel patch" tutorial on the
kernelnewbies.org site for a good example of how to do all of this.

Also the Documentation/SubmittingPatches file in the kernel source tree
should help out.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Baole Fang <fbl718@163.com>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Jeremy Szu <jeremy.szu@canonical.com>,
	Werner Sembach <wse@tuxedocomputers.com>,
	Hui Wang <hui.wang@canonical.com>,
	Cameron Berkenpas <cam@neo-zeon.de>,
	Kailang Yang <kailang@realtek.com>, Sami Loone <sami@loone.fi>,
	Elia Devito <eliadevito@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Legion Y9000X 2020
Date: Wed, 5 Jan 2022 12:44:21 +0100	[thread overview]
Message-ID: <YdWElRjkZ0lybrMJ@kroah.com> (raw)
In-Reply-To: <757a4402-1067-e3c8-8ca3-43ee62047ebe@163.com>

On Wed, Jan 05, 2022 at 07:39:33PM +0800, Baole Fang wrote:
> Sorry, this is my first time to submit patch to Linux, so I'm not quite
> familiar with the convention. Since I was changing based on v5.15.12 and I
> saw others mentioning their upstream commit, I included the that commit id.

Those commits were coming from the stable backports only, they were not
done by the original author.

> Please forgive me and tell me what is supposed to be done if possible. I
> still have a lot to learn.

Please take a look at the "first kernel patch" tutorial on the
kernelnewbies.org site for a good example of how to do all of this.

Also the Documentation/SubmittingPatches file in the kernel source tree
should help out.

thanks,

greg k-h

  reply	other threads:[~2022-01-05 11:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05  3:41 [PATCH] ALSA: hda/realtek: Add quirk for Legion Y9000X 2020 Baole Fang
2022-01-05  8:26 ` Takashi Iwai
2022-01-05  8:26   ` Takashi Iwai
2022-01-05 10:55   ` Greg Kroah-Hartman
2022-01-05 10:55     ` Greg Kroah-Hartman
2022-01-05 11:39     ` Baole Fang
2022-01-05 11:39       ` Baole Fang
2022-01-05 11:44       ` Greg Kroah-Hartman [this message]
2022-01-05 11:44         ` Greg Kroah-Hartman
2022-01-05 12:29         ` Baole Fang
2022-01-05 12:29           ` Baole Fang
2022-01-05 12:33           ` Greg Kroah-Hartman
2022-01-05 12:33             ` Greg Kroah-Hartman
2022-01-05 12:53             ` Baole Fang
2022-01-05 12:53               ` Baole Fang
  -- strict thread matches above, loose matches on Subject: below --
2022-01-05 14:08 Baole Fang
2022-01-05 15:43 ` Takashi Iwai
2022-01-05 15:43   ` Takashi Iwai

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=YdWElRjkZ0lybrMJ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cam@neo-zeon.de \
    --cc=eliadevito@gmail.com \
    --cc=fbl718@163.com \
    --cc=hui.wang@canonical.com \
    --cc=jeremy.szu@canonical.com \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sami@loone.fi \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    --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.