From: Pavel Machek <pavel@ucw.cz>
To: Merlijn Wajer <merlijn@wizzup.org>
Cc: linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Darren Hart (VMware)" <dvhart@infradead.org>,
"Mattias Jacobsson" <2pi@mok.nu>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH 0/2] Add SW_MACHINE_COVER key
Date: Tue, 9 Jun 2020 13:21:59 +0200 [thread overview]
Message-ID: <20200609112159.GB2523@amd> (raw)
In-Reply-To: <60f55d93-e7d3-15e7-3b34-00e3e3eda99c@wizzup.org>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
Hi!
> A while later (again) - any thoughts/comments?
>
> Should I resend the series?
Sorry, I did not see this before. Can you cc me on the next patch
iteration?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-06-09 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 17:02 [PATCH 0/2] Add SW_MACHINE_COVER key Merlijn Wajer
2020-02-15 17:02 ` [PATCH 1/2] Input: add `SW_MACHINE_COVER` Merlijn Wajer
2020-02-15 17:02 ` [PATCH 2/2] ARM: dts: n900: remove mmc1 card detect gpio Merlijn Wajer
2020-02-25 14:31 ` [PATCH 0/2] Add SW_MACHINE_COVER key Tony Lindgren
2020-04-15 13:29 ` Merlijn Wajer
2020-06-08 23:56 ` Merlijn Wajer
2020-06-09 11:21 ` Pavel Machek [this message]
2020-06-12 12:53 Merlijn Wajer
2020-06-16 10:50 ` Pavel Machek
2020-06-30 19:29 ` Dmitry Torokhov
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=20200609112159.GB2523@amd \
--to=pavel@ucw.cz \
--cc=2pi@mok.nu \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=merlijn@wizzup.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tony@atomide.com \
/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).