From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Luke Jones <luke@ljones.dev>, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-input <linux-input@vger.kernel.org>,
Andy Shevchenko <andy@infradead.org>
Subject: Re: [PATCH V6 RESEND] HID: ASUS: Add support for ASUS N-Key keyboard
Date: Mon, 12 Oct 2020 13:14:57 +0300 [thread overview]
Message-ID: <CAHp75VfZ3QmePN2fLmAZPd1rMPzWHB=F8t4fs5s6R9rbQdvDww@mail.gmail.com> (raw)
In-Reply-To: <4253ebb9-8978-7f31-3931-b2f5bd327f0d@redhat.com>
On Mon, Oct 12, 2020 at 12:51 PM Hans de Goede <hdegoede@redhat.com> wrote:
> On 10/11/20 9:05 AM, Luke Jones wrote:
> > On Fri, Oct 9, 2020 at 16:22, Hans de Goede <hdegoede@redhat.com> wrote:
...
> > All the DSL we've dumped are here:
> > https://gitlab.com/asus-linux/reverse-engineering/-/tree/master/dsl
> >
> > I'm not sure where to go from here. Do I resubmit the revised patch in a new thread
> > or should I attach here? (I'll attach for now)
>
> Please submit a new version in a new email thread with [PATCH v2] as prefix to the
> subject, you can do this by passing --subject-prefix="PATCH v2" to git format-patch.
-v<N> will do it for you in a shorter way.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-10-12 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 21:56 [PATCH V6 RESEND] HID: ASUS: Add support for ASUS N-Key keyboard Luke D Jones
2020-10-08 9:33 ` Luke Jones
2020-10-09 9:38 ` Jiri Kosina
2020-10-09 13:14 ` Andy Shevchenko
2020-10-09 13:37 ` Hans de Goede
2020-10-09 14:03 ` Andy Shevchenko
2020-10-09 14:22 ` Hans de Goede
2020-10-11 7:05 ` Luke Jones
2020-10-12 9:51 ` Hans de Goede
2020-10-12 10:14 ` Andy Shevchenko [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='CAHp75VfZ3QmePN2fLmAZPd1rMPzWHB=F8t4fs5s6R9rbQdvDww@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
/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;
as well as URLs for NNTP newsgroup(s).