From: Hans de Goede <hdegoede@redhat.com>
To: Darren Hart <dvhart@infradead.org>, Paul Cercueil <paul@crapouillou.net>
Cc: Andy Shevchenko <andy@infradead.org>,
linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: silead_dmi: Add entry for the Teclast X98 Plus II
Date: Wed, 3 Jan 2018 09:01:34 +0100 [thread overview]
Message-ID: <5c5301e1-48f5-5762-b1d8-95e5f4a2bd8d@redhat.com> (raw)
In-Reply-To: <20180102234033.GB24794@fury>
Hi,
On 03-01-18 00:40, Darren Hart wrote:
> On Tue, Jan 02, 2018 at 07:39:27PM +0100, Paul Cercueil wrote:
>> Add touchscreen platform data for the Teclast X98 Plus II tablet.
>>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> Acked-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> drivers/platform/x86/silead_dmi.c | 24 ++++++++++++++++++++++++
>> 1 file changed, 24 insertions(+)
>>
>> v2: Rebased on top of http://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git/shortlog/refs/heads/review-andy
>
> Generally "testing" is the branch you want to base on if linus/master
> doesn't work as the review-* branches *will* rebase frequently.
> Exceptions exist of course, and this patch is just fine - just for
> future reference.
This is my "fault", I asked Paul to rebase on top of
review-andy as that had 1 new silead_dmi patches missing
from testing, so otherwise we would end up with a conflict when
merging review branches. Same reason why I've been basing my
silead_dmi patches on top of review-andy even though that is
an unusual base to use.
Regards,
Hans
next prev parent reply other threads:[~2018-01-03 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 13:42 [PATCH] " Paul Cercueil
2018-01-02 15:34 ` Hans de Goede
2018-01-02 18:39 ` [PATCH v2] " Paul Cercueil
2018-01-02 23:40 ` Darren Hart
2018-01-03 8:01 ` Hans de Goede [this message]
2018-01-03 14:10 ` Andy Shevchenko
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=5c5301e1-48f5-5762-b1d8-95e5f4a2bd8d@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=platform-driver-x86@vger.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®