From: "Karel Balej" <karelb@gimli.ms.mff.cuni.cz>
To: "Markuss Broks" <markuss.broks@gmail.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Henrik Rydberg" <rydberg@bitmath.org>,
<linux-input@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<~postmarketos/upstreaming@lists.sr.ht>
Cc: "Duje Mihanović" <duje.mihanovic@skole.hr>
Subject: Re: [PATCH v2 0/5] input/touchscreen: imagis: add support for IST3032C
Date: Tue, 03 Oct 2023 15:45:18 +0200 [thread overview]
Message-ID: <CVYULJSWIJHC.61H4AAIMA9I4@gimli.ms.mff.cuni.cz> (raw)
In-Reply-To: <20231003133440.4696-1-karelb@gimli.ms.mff.cuni.cz>
Hello,
> From: Karel Balej <karelb@gimli.ms.mff.cuni.cz>
I am very sorry, I wanted to use a different email address for sending
than for commiting so that the message would also reach people whose
email providers have more strict requirements on sender authentication
(such as Google), but it seems that I have made a mistake and confused
git altogether.
I will fix it in a possible v3 after I receive some feedback or I will
resend it before it gets applied and I will make sure to properly test
the setup then.
My apologies,
K. B.
prev parent reply other threads:[~2023-10-03 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 13:34 karelb
2023-10-03 13:34 ` [PATCH v2 1/5] input/touchscreen: imagis: Correct the maximum touch area value karelb
2023-10-03 13:34 ` [PATCH v2 2/5] dt-bindings: input/touchscreen: Add compatible for IST3038B karelb
2023-10-04 8:09 ` Krzysztof Kozlowski
2023-10-04 8:32 ` Karel Balej
2023-10-03 13:34 ` [PATCH v2 3/5] input/touchscreen: imagis: Add support for Imagis IST3038B karelb
2023-10-04 2:50 ` kernel test robot
2023-10-03 13:34 ` [PATCH v2 4/5] dt-bindings: input/touchscreen: imagis: add compatible for IST3032C karelb
2023-10-03 13:34 ` [PATCH v2 5/5] input/touchscreen: imagis: add support " karelb
2023-10-04 6:42 ` kernel test robot
2023-10-03 13:45 ` Karel Balej [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=CVYULJSWIJHC.61H4AAIMA9I4@gimli.ms.mff.cuni.cz \
--to=karelb@gimli.ms.mff.cuni.cz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=duje.mihanovic@skole.hr \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markuss.broks@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rydberg@bitmath.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®