From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, Andrew Dunai <a@dun.ai>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH] Add support for Vinga Twizzle J116 Silead touchscreen
Date: Tue, 5 May 2020 13:55:40 +0300 [thread overview]
Message-ID: <CAHp75VfUUwGyM97Fzh+u1hAFmjdyYinrYE=a+eAwuCNjchq4Qw@mail.gmail.com> (raw)
In-Reply-To: <f4aeeb2c-32c4-e2a8-193e-2b4d892da4db@redhat.com>
On Tue, May 5, 2020 at 12:02 PM Hans de Goede <hdegoede@redhat.com> wrote:
> On 5/4/20 8:20 PM, Randy Dunlap wrote:
> > Usually you need to send patches to a maintainer who could then
> > merge/apply them.
>
> From a code point-of-view this looks good to me.
>
> Andrew, if you can resend this to the proper folks (including me)
> with a proper Signed-off-by (*), then this should be ready for merging.
>
> Regards,
>
> Hans
>
>
> *) that might have already been there, but it wasn't present in
> the part quoted by Randy
Luckily I see the original message. There is neither Sob nor commit
message. They must to be present.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-05-05 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200504164514.18641-1-a@dun.ai>
2020-05-04 18:20 ` [PATCH] Add support for Vinga Twizzle J116 Silead touchscreen Randy Dunlap
2020-05-05 8:38 ` Andy Shevchenko
2020-05-05 9:01 ` Hans de Goede
2020-05-05 10:55 ` 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='CAHp75VfUUwGyM97Fzh+u1hAFmjdyYinrYE=a+eAwuCNjchq4Qw@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=a@dun.ai \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).