From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: 조준완 <junwan.cho@samsung.com>
Cc: "Jiri Kosina" <jikos@kernel.org>,
"michael.zaidman@gmail.com" <michael.zaidman@gmail.com>,
"erazor_de@users.sourceforge.net"
<erazor_de@users.sourceforge.net>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
"alexandre.torgue@foss.st.com" <alexandre.torgue@foss.st.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
김일호 <ih0923.kim@samsung.com>, 박천호 <chun.ho.park@samsung.com>,
배윤식 <yunsik.bae@samsung.com>, 강대희 <daihee7.kang@samsung.com>,
이광호 <gaudium.lee@samsung.com>, 류천우 <chunwoo.ryu@samsung.com>,
나두수 <doosu.na@samsung.com>, 김수현 <suhyun_.kim@samsung.com>
Subject: Re: (2) (3) (2) (2) Request for reverting the commit for Samsung HID driver
Date: Wed, 30 Mar 2022 11:26:29 +0200 [thread overview]
Message-ID: <YkQiRTve9ZXRhoG7@kroah.com> (raw)
In-Reply-To: <20220330092058epcms1p799e10561617c02a14d5d8b413722f678@epcms1p7>
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, Mar 30, 2022 at 06:20:58PM +0900, 조준완 wrote:
>
> No. If so, I will not apply in house patches.
I do not understand what you are referencing here, sorry. Please
explain.
> I'm a Bluetooth person, and I'm only interested in Bluetooth devices.
That's fine, but this driver, as is in the tree today, does not support
bluetooth devices. Please submit a patch to resolve that.
> Codes for Bluetooth devices will never be worked along the commit, anyway, no reason to include them.
I do not understand. Please explain.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-30 9:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220330062122epcms1p30a2c2e3e1d3b108d729a00034bf86587@epcms1p3>
[not found] ` <20220330062122epcms1p30a2c2e3e1d3b108d729a00034bf86587@epcms1p3>
2022-03-30 6:40 ` Request for reverting the commit for Samsung HID driver gregkh
[not found] ` <20220330070159epcms1p31c351bc7eb90d99e0bbecd2c2f6092d1@epcms1p3>
2022-03-30 7:52 ` Jiri Kosina
2022-03-30 8:09 ` 조준완
2022-03-30 8:11 ` Jiri Kosina
2022-03-30 8:14 ` (2) " gregkh
2022-03-30 8:23 ` 조준완
2022-03-30 8:27 ` Jiri Kosina
2022-03-30 8:32 ` (2) " gregkh
2022-03-30 8:44 ` 조준완
2022-03-30 8:49 ` Jiri Kosina
2022-03-30 9:01 ` 조준완
2022-03-30 9:13 ` (3) " gregkh
2022-03-30 9:20 ` 조준완
2022-03-30 9:26 ` gregkh [this message]
2022-03-30 9:43 ` RE:(2) (2) " 조준완
2022-03-30 9:49 ` (2) " gregkh
2022-03-30 9:58 ` 조준완
2022-03-30 18:43 ` Krzysztof Kozlowski
2022-03-31 1:51 ` 조준완
2022-03-31 4:22 ` (2) " gregkh
2022-03-30 9:12 ` (2) (2) " gregkh
2022-03-30 7:56 ` gregkh
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=YkQiRTve9ZXRhoG7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.torgue@foss.st.com \
--cc=chun.ho.park@samsung.com \
--cc=chunwoo.ryu@samsung.com \
--cc=daihee7.kang@samsung.com \
--cc=doosu.na@samsung.com \
--cc=erazor_de@users.sourceforge.net \
--cc=gaudium.lee@samsung.com \
--cc=ih0923.kim@samsung.com \
--cc=jikos@kernel.org \
--cc=junwan.cho@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.zaidman@gmail.com \
--cc=stable@vger.kernel.org \
--cc=suhyun_.kim@samsung.com \
--cc=yunsik.bae@samsung.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.