From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: qcom: lpass-lpi: allow slew rate bit in main pin config register
Date: Mon, 23 Oct 2023 10:22:51 +0200 [thread overview]
Message-ID: <8f608e3c-a282-4df2-abcd-8e38efc35843@linaro.org> (raw)
In-Reply-To: <CACRpkdZUSkr2MLB870Y5O2Qxvbnz++XUKMm+BXG1yx9vrOEvwA@mail.gmail.com>
On 23/10/2023 10:19, Linus Walleij wrote:
> On Fri, Oct 13, 2023 at 4:59 PM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>
>
>> Changes in v2
>
> I tried to apply this to the pinctrl devel branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel
>
> It doesn't apply, could you rebase it?
The context depends on my previous fix which you applied and sent for
v6.6 already:
https://lore.kernel.org/linux-arm-msm/CACRpkdaybnYEmkgv7VG4fh5sXQ7uwHm2wH2Khja-P1b6idYr8w@mail.gmail.com/
I can rebase, but I am afraid it will cause conflicts. Is it reasonable
for you to merge v6.6-rc7 into your devel branch?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-23 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 14:59 [PATCH v2 0/2] pinctrl: qcom: lpass-lpi: allow slew rate bit in main pin config register Krzysztof Kozlowski
2023-10-13 14:59 ` [PATCH v2 1/2] pinctrl: qcom: lpass-lpi: split slew rate set to separate function Krzysztof Kozlowski
2023-10-18 8:51 ` Konrad Dybcio
2023-10-13 14:59 ` [PATCH v2 2/2] pinctrl: qcom: lpass-lpi: allow slew rate bit in main pin config register Krzysztof Kozlowski
2023-10-18 9:00 ` Konrad Dybcio
2023-11-14 7:45 ` Linus Walleij
2023-10-23 8:19 ` [PATCH v2 0/2] " Linus Walleij
2023-10-23 8:22 ` Krzysztof Kozlowski [this message]
2023-10-23 8:27 ` Linus Walleij
2023-10-23 8:48 ` Krzysztof Kozlowski
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=8f608e3c-a282-4df2-abcd-8e38efc35843@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).