From: Chris Ye <linzhao.ye@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Chris Ye <lzye@google.com>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
trivial@kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>
Subject: Re: [PATCH] Add devices for HID_QUIRK_INCREMENT_USAGE_ON_DUPLICATE
Date: Sun, 1 Nov 2020 12:34:28 -0800 [thread overview]
Message-ID: <a18b62e9-2c40-c20c-9822-13e0a9930aeb@gmail.com> (raw)
In-Reply-To: <20201030104831.GD2395528@kroah.com>
Thanks Greg, I just sent out the v2 version of patches, to maintainers
of HID core layer.
On 10/30/20 3:48 AM, Greg KH wrote:
> 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 Thu, Oct 29, 2020 at 01:04:06PM -0700, Chris Ye wrote:
>> Hi Greg,
>>
>> Yes, I can see them on https://lore.kernel.org/linux-input/ now.
>>
>> But I didn't put [PATCH v1] in subject, should I sent them again with
>> version?
> It should be v2 at the least, right? And please read the documentation
> for how to do that properly.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2020-11-01 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 23:51 FirstName LastName
2020-10-29 5:41 ` Greg KH
[not found] ` <CAFFudd+7DrJ+vYZ5wQ58mei6VMkMPGCpS1d7DwZMrzM-FVKzqQ@mail.gmail.com>
2020-10-29 19:14 ` Greg KH
2020-10-29 20:04 ` Chris Ye
2020-10-30 10:48 ` Greg KH
2020-11-01 20:34 ` Chris Ye [this message]
2020-10-29 0:00 Chris Ye
2020-10-29 19:47 Chris Ye
2020-10-29 20:39 ` Dmitry Torokhov
2020-11-01 20:35 ` Chris Ye
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=a18b62e9-2c40-c20c-9822-13e0a9930aeb@gmail.com \
--to=linzhao.ye@gmail.com \
--cc=alexandru.ardelean@analog.com \
--cc=benjamin.tissoires@redhat.com \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lzye@google.com \
--cc=stable@vger.kernel.org \
--cc=trivial@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®