From: Lucas Stach <l.stach@pengutronix.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, kernel@pengutronix.de,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH v2 1/4] Input: exc3000: split MT event handling from IRQ handler
Date: Mon, 10 Aug 2020 18:49:45 +0200 [thread overview]
Message-ID: <9be441d3943f2a7f625be7ec6c1fc79dd84db6c3.camel@pengutronix.de> (raw)
In-Reply-To: <20200810162720.GR1665100@dtor-ws>
Am Montag, den 10.08.2020, 09:27 -0700 schrieb Dmitry Torokhov:
> Hi Lucas,
>
> On Mon, Aug 10, 2020 at 02:40:30PM +0200, Lucas Stach wrote:
> > Hi Dmitry,
> >
> > Am Montag, den 18.05.2020, 15:24 +0200 schrieb Lucas Stach:
> > > Hi Dmitry,
> > >
> > > any chance you could take a look at this series?
> >
> > Are you able to find some time to look at this series? Should I resend
> > the series?
>
> Sorry about delays. Could you please resend as I applied another se5ries
> to this driver?
Urgh, this may take me some time, as the other series collides quite
badly with this one and adds some of the same bits (firmware version
query). So I'll need to do some rework of the series, requiring a full
round of testing. :(
Regards,
Lucas
prev parent reply other threads:[~2020-08-10 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 14:33 [PATCH v2 1/4] Input: exc3000: split MT event handling from IRQ handler Lucas Stach
2020-03-13 14:33 ` [PATCH v2 2/4] Input: exc3000: query and show type, model and firmware revision info Lucas Stach
2020-03-13 14:33 ` [PATCH v2 3/4] Input: exc3000: expose type, model and firmware revision as sysfs attributes Lucas Stach
2020-03-13 14:33 ` [PATCH v2 4/4] Input: exc3000: add firmware update support Lucas Stach
2020-05-18 13:24 ` [PATCH v2 1/4] Input: exc3000: split MT event handling from IRQ handler Lucas Stach
2020-08-10 12:40 ` Lucas Stach
2020-08-10 16:27 ` Dmitry Torokhov
2020-08-10 16:49 ` Lucas Stach [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=9be441d3943f2a7f625be7ec6c1fc79dd84db6c3.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-input@vger.kernel.org \
--cc=patchwork-lst@pengutronix.de \
/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).