From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: qaz6750 lzy <qaz6750@outlook.com>,
agross@kernel.org, andersson@kernel.org
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
krzysztof.kozlowski@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: sm8150: Fix the I2C7 interrupt
Date: Tue, 25 Jul 2023 09:42:06 +0200 [thread overview]
Message-ID: <f71c6097-9e9c-0edd-6d96-262ba34712e2@linaro.org> (raw)
In-Reply-To: <SY7P282MB3787D64A586E9DC55547BB2DB203A@SY7P282MB3787.AUSP282.PROD.OUTLOOK.COM>
On 25.07.2023 07:55, qaz6750 lzy wrote:
> On 25/07/2023 13:50, qaz6750 lzy wrote:
>> On 25/07/2023 04:33, qaz6750 lzy wrote:
>>> I2C6 and I2C7 use the same interrupts, which is incorrect.
>>> In the downstream kernel, I2C7 has interrupts of 608 instead of 607.
>>>
>>> Signed-off-by: qaz6750 lzy <qaz6750@outlook.com>
>>
>> Neither From field nor Signed-off-by have the full name you mentioned
> before.
>>
>> Also: Do not attach (thread) your patchsets to some other threads
>> (unrelated or older versions). This buries them deep in the mailbox and
>> might interfere with applying entire sets.
>
> I'm sorry, this is my problem. As this is my first time submitting a patch,
> I made some mistakes. So, what else do I need to do now? Thank you
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Konrad
next prev parent reply other threads:[~2023-07-25 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 16:21 [PATCH] " qaz6750
2023-07-24 16:29 ` Konrad Dybcio
2023-07-24 16:52 ` Krzysztof Kozlowski
2023-07-24 16:53 ` Konrad Dybcio
2023-07-25 1:46 ` qaz6750
2023-07-25 2:33 ` [PATCH v2] " qaz6750 lzy
2023-07-25 5:30 ` Krzysztof Kozlowski
2023-07-25 5:55 ` qaz6750 lzy
2023-07-25 7:42 ` Konrad Dybcio [this message]
2023-07-25 8:42 [PATCH V2] " qaz6750 lzy
2023-07-26 18:46 ` Krzysztof Kozlowski
2023-07-26 18:46 ` Konrad Dybcio
2023-07-26 20:10 ` Dmitry Baryshkov
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=f71c6097-9e9c-0edd-6d96-262ba34712e2@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qaz6750@outlook.com \
--cc=robh+dt@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®