From: David Heidelberg <david@ixit.cz>
To: Muzaffer Kadir <muzafferkadir@mainlining.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
Ulf Hansson <ulfh@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>, Lee Jones <lee@kernel.org>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Robert Marko <robimarko@gmail.com>,
Guru Das Srinagesh <linux@gurudas.dev>,
Amit Kucheria <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>, Kees Cook <kees@kernel.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Dang Huynh <danct12@riseup.net>,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
iommu@lists.linux.dev, mfd@lists.linux.dev,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-pm@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH RFC 20/20] arm64: dts: qcom: generalmobile-shamrock: new device
Date: Mon, 14 Sep 2026 14:05:17 +0200 [thread overview]
Message-ID: <158555ee-315b-45c5-a2a7-c98ea104d540@ixit.cz> (raw)
In-Reply-To: <be018c1c-88f3-41fc-9293-d5090a79b3a7@ixit.cz>
On 14/09/2026 14:03, David Heidelberg wrote:
> On 14/09/2026 13:58, Muzaffer Kadir wrote:
>> Hi Konrad,
>>
>> On Mon, 14 Sep 2026 13:22:52 +0200, Konrad Dybcio wrote:
>>> On 9/12/26 10:39 AM, Muzaffer Kadir via B4 Relay wrote:
>>>> From: Muzaffer Kadir <muzafferkadir@mainlining.org>
>>>>
>>>> Add General Mobile Shamrock (GM 5 Plus).
>>>> Shamrock is designed similar to L9300.
>>>> Downstream reference is [1].
>>>
>>> Please feel free to
>>> wrap your messages at 72
>>> characters, otherwise they are
>>> a bit hard to read! :D
>>
>> I am sorry to hear that. vim shows
>> it less than 72 and I can't see which
>> line is bigger than 72.
>
> Hehe, yeah, had the same issue.
>
> require('lualine').setup {
> options = {
> icons_enabled = true,
> theme = 'auto',
> component_separators = { left = '', right = '|'},
> section_separators = { left = '', right = ''},
> disabled_filetypes = {
> statusline = {},
> winbar = {},
> },
> ignore_focus = {},
> always_divide_middle = true,
> globalstatus = false,
> refresh = {
> statusline = 1000,
> tabline = 1000,
> winbar = 1000,
> }
> },
> sections = {
> lualine_a = {'mode'},
> lualine_b = {'branch', 'diff', 'diagnostics'},
> lualine_c = {'filename'},
> lualine_x = {'filetype'},
> lualine_y = {'progress'},
> lualine_z = {
> { '%3l:%-2.(%c%V%)', type = 'stl' },
> },
> },
> inactive_sections = {
> lualine_a = {},
> lualine_b = {},
> lualine_c = {'filename'},
> lualine_x = {'location'},
> lualine_y = {},
> lualine_z = {}
> },
> tabline = {},
> winbar = {},
>
> inactive_winbar = {},
>
> extensions = {}
>
> }
>
> see a lualine_z for the way how to let neovim show length INCLUDING tabs :)
...aaaand the comment was about opposite problem then the one I tried to address.
Sorry for the noise.
>
> David
>
>> Only one I can see is url itself.
>> Should I move url to Link trailer?
>>
>> For other parts of review,
>> I will fix them in v2.
>> Thanks a lot for review.
>>
>> Best regards,
>> Muzaffer Kadir
>
prev parent reply other threads:[~2026-09-14 12:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 8:39 [PATCH RFC 00/20] Add Initial Support For MSM8952, Add General Mobile Shamrock Muzaffer Kadir via B4 Relay
2026-09-12 8:39 ` [PATCH RFC 01/20] dt-bindings: clock: qcom: Add MSM8952 global clock controller Muzaffer Kadir via B4 Relay
2026-09-12 8:45 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 02/20] clk: qcom: Add global clock controller driver for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-12 8:54 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 03/20] dt-bindings: nvmem: Add compatible " Muzaffer Kadir via B4 Relay
2026-09-12 8:42 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 04/20] dt-bindings: power: rpmpd: Add MSM8952 power domains Muzaffer Kadir via B4 Relay
2026-09-12 8:42 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 05/20] dt-bindings: mmc: sdhci-msm: Add MSM8952 compatible Muzaffer Kadir via B4 Relay
2026-09-12 8:43 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 06/20] dt-bindings: vendor-prefixes: Add General Mobile Muzaffer Kadir via B4 Relay
2026-09-12 8:41 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 07/20] dt-bindings: arm: qcom: Document MSM8952 SoC binding Muzaffer Kadir via B4 Relay
2026-09-12 8:48 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 08/20] dt-bindings: iommu: qcom,iommu: Add MSM8952 IOMMU to SMMUv2 compatibles Muzaffer Kadir via B4 Relay
2026-09-12 8:42 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 09/20] dt-bindings: mfd: qcom,tcsr: Add compatible for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-12 8:42 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 10/20] dt-bindings: display/msm: qcom, mdp5: Add MSM8952 compatible Muzaffer Kadir via B4 Relay
2026-09-12 8:47 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 11/20] dt-bindings: firmware: qcom,scm: Document MSM8952 SCM Muzaffer Kadir via B4 Relay
2026-09-12 8:44 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 12/20] dt-bindings: clock: qcom,rpmcc: Add MSM8952 compatible Muzaffer Kadir via B4 Relay
2026-09-12 8:46 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 13/20] clk: qcom: smd-rpm: Add clocks for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-12 8:46 ` sashiko-bot
2026-09-14 11:18 ` Konrad Dybcio
2026-09-12 8:39 ` [PATCH RFC 14/20] drm: msm: mdp5: Add MDP5 configuration " Muzaffer Kadir via B4 Relay
2026-09-12 9:19 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 15/20] soc: qcom: ubwc: Add UBWC config " Muzaffer Kadir via B4 Relay
2026-09-12 8:43 ` sashiko-bot
2026-09-14 11:23 ` Konrad Dybcio
2026-09-14 14:21 ` Abel Vesa
2026-09-12 8:39 ` [PATCH RFC 16/20] dt-bindings: thermal: tsens: Add MSM8952 Muzaffer Kadir via B4 Relay
2026-09-12 8:51 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 17/20] thermal: qcom: tsens: Add support for MSM8952 tsens Muzaffer Kadir via B4 Relay
2026-09-12 8:51 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 18/20] arm64: dts: qcom: Add initial support for MSM8952 Muzaffer Kadir via B4 Relay
2026-09-12 8:56 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 19/20] dt-bindings: input: touchscreen: goodix: Add binding for GT970 Muzaffer Kadir via B4 Relay
2026-09-12 8:50 ` sashiko-bot
2026-09-12 8:39 ` [PATCH RFC 20/20] arm64: dts: qcom: generalmobile-shamrock: new device Muzaffer Kadir via B4 Relay
2026-09-12 8:58 ` sashiko-bot
2026-09-12 15:47 ` David Heidelberg
2026-09-12 17:42 ` Muzaffer Kadir
2026-09-14 11:22 ` Konrad Dybcio
2026-09-14 11:58 ` Muzaffer Kadir
2026-09-14 12:01 ` Konrad Dybcio
2026-09-14 12:03 ` David Heidelberg
2026-09-14 12:05 ` David Heidelberg [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=158555ee-315b-45c5-a2a7-c98ea104d540@ixit.cz \
--to=david@ixit.cz \
--cc=abelvesa@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=amitk@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=danct12@riseup.net \
--cc=daniel.lezcano@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=gpiccoli@igalia.com \
--cc=iommu@lists.linux.dev \
--cc=jbrunet+clk@baylibre.com \
--cc=jesszhan0024@gmail.com \
--cc=joro@8bytes.org \
--cc=kees@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@gurudas.dev \
--cc=lukasz.luba@arm.com \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mfd@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=muzafferkadir@mainlining.org \
--cc=phone-devel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=robin.murphy@arm.com \
--cc=rui.zhang@intel.com \
--cc=sboyd@kernel.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=srini@kernel.org \
--cc=thara.gopinath@gmail.com \
--cc=tony.luck@intel.com \
--cc=tzimmermann@suse.de \
--cc=ulfh@kernel.org \
--cc=will@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).