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 13:33:48 +0100 [thread overview]
Message-ID: <YdWQLOtV8Tz8ArrH@kroah.com> (raw)
In-Reply-To: <6bf35d26-73d4-ba14-f931-8d379c623482@163.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Jan 05, 2022 at 08:29:26PM +0800, Baole Fang wrote:
> Thank you for your explanation! I shouldn't have written that line and I
> supposed it can be ignored. Is there anything else I could do?
We can not just "ignore" it, you need to fix your change up and resend
it in a proper format so that it can be applied.
As-is, it is not acceptable, sorry.
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: 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 13:33:48 +0100 [thread overview]
Message-ID: <YdWQLOtV8Tz8ArrH@kroah.com> (raw)
In-Reply-To: <6bf35d26-73d4-ba14-f931-8d379c623482@163.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Jan 05, 2022 at 08:29:26PM +0800, Baole Fang wrote:
> Thank you for your explanation! I shouldn't have written that line and I
> supposed it can be ignored. Is there anything else I could do?
We can not just "ignore" it, you need to fix your change up and resend
it in a proper format so that it can be applied.
As-is, it is not acceptable, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-05 12:33 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
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 [this message]
2022-01-05 12:33 ` Greg Kroah-Hartman
2022-01-05 12:53 ` Baole Fang
2022-01-05 12:53 ` Baole Fang
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=YdWQLOtV8Tz8ArrH@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=perex@perex.cz \
--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.