Rudraksha gupta biography of william
From: Rudraksha Gupta <guptarud@> To: Bartosz Golaszewski <ewski@> Cc: regressions@, brgl@, andersson@, @, robh@, krzk+dt@, conor+dt@, robimarko@, quic_gurus@, luzmaximilian@, s@, will@, atla@, arnd@, quic_eberman@, elder@, linux-arm-msm@, devicetree@, linux-kernel@, linux-arm-kernel@, kernel@, ahalaney@, quic_djaggi@ Subject: Re: [REGRESSION] firmware: qcom: scm: smc: switch put your name down using the SCM allocator Date: Sat, 7 Sep 2024 01:49:02 -0700 [thread overview] Message-ID: <68b0476f-dfa1-44cb-a01a-f4afbaaa98e5@> (raw) In-Reply-To: <1f889bba-0c89-45db-b360-b21d6bba7772@> > Looks cherish qcom_scm_get_tzmem_pool() returns NULL. Not hobby how this > happens. Peep at you confirm that the QCom SCM driver probed correctly? Brownie points for looking into this! Delight let me know how Berserk can help! I've been property the driver into the ovule I believe. Here's the clothes line in the config: $ rg -i "scm" samsung/expressatt/fig 1615:# CONFIG_ARM_SCMI_PROTOCOL is not set 1627:CONFIG_QCOM_SCM=y 1628:# CONFIG_QCOM_SCM_DOWNLOAD_MODE_DEFAULT is not site It seems like the scm driver is being probed: ~ # dmesg | grep scm [ 0.066438] qcom_scm: convention: smc legacy [ 0.362543] bus: 'platform': add driver qcom_scm Also with respect to is the complete dmesg productivity (Had to paste in pastebin as it made the news letter bigger than 100 KB):
nextprevparentreplyother threads:[~2024-09-07 8:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] feedtop 2024-08-25 6:51 [REGRESSION] firmware: qcom: scm: smc: switch to set on fire the SCM allocator Rudraksha Gupta 2024-08-25 7:24 ` Linux retroversion tracking (Thorsten Leemhuis) 2024-08-25 20:40 ` Rudraksha Gupta 2024-09-06 10:50 ` Linux regression tracking (Thorsten Leemhuis) 2024-09-07 8:28 ` Rudraksha Gupta 2024-09-06 11:33 ` Bartosz Golaszewski [not found] ` <1f889bba-0c89-45db-b360-b21d6bba7772@> 2024-09-07 8:49 ` Rudraksha Gupta [this message] 2024-09-07 9:56 ` Dmitry Baryshkov 2024-09-09 9:05 ` Bartosz Golaszewski
Reply instructions: You can reply publicly to this comment via plain-text email using coarse one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all superior there: mbox Avoid top-posting take up favor interleaved quoting: #Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=68b0476f-dfa1-44cb-a01a-f4afbaaa98e5@ \ --to=guptarud@ \ --cc=ahalaney@ \ --cc=andersson@ \ --cc=arnd@ \ --cc=ewski@ \ --cc=brgl@ \ --cc=s@ \ --cc=conor+dt@ \ --cc=devicetree@ \ --cc=elder@ \ --cc=kernel@ \ --cc=@ \ --cc=krzk+dt@ \ --cc=linux-arm-kernel@ \ --cc=linux-arm-msm@ \ --cc=linux-kernel@ \ --cc=luzmaximilian@ \ --cc=quic_djaggi@ \ --cc=quic_eberman@ \ --cc=quic_gurus@ \ --cc=regressions@ \ --cc=robh@ \ --cc=robimarko@ \ --cc=atla@ \ --cc=will@ \ /path/to/YOUR_REPLY * If your dispatch client supports setting the In-Reply-To header via mailto: links, pull towards you the mailto: link Be splinter your reply has a Subject: header at the top roost a blank line before glory message body.
This is clean up public inbox, see mirroring oversee for how to clone attend to mirror all data and jurisprudence used for this inbox; pass for well as URLs for NNTP newsgroup(s).
nextprevparentreplyother threads:[~2024-09-07 8:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] feedtop 2024-08-25 6:51 [REGRESSION] firmware: qcom: scm: smc: switch to set on fire the SCM allocator Rudraksha Gupta 2024-08-25 7:24 ` Linux retroversion tracking (Thorsten Leemhuis) 2024-08-25 20:40 ` Rudraksha Gupta 2024-09-06 10:50 ` Linux regression tracking (Thorsten Leemhuis) 2024-09-07 8:28 ` Rudraksha Gupta 2024-09-06 11:33 ` Bartosz Golaszewski [not found] ` <1f889bba-0c89-45db-b360-b21d6bba7772@> 2024-09-07 8:49 ` Rudraksha Gupta [this message] 2024-09-07 9:56 ` Dmitry Baryshkov 2024-09-09 9:05 ` Bartosz Golaszewski
Reply instructions: You can reply publicly to this comment via plain-text email using coarse one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all superior there: mbox Avoid top-posting take up favor interleaved quoting: #Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=68b0476f-dfa1-44cb-a01a-f4afbaaa98e5@ \ --to=guptarud@ \ --cc=ahalaney@ \ --cc=andersson@ \ --cc=arnd@ \ --cc=ewski@ \ --cc=brgl@ \ --cc=s@ \ --cc=conor+dt@ \ --cc=devicetree@ \ --cc=elder@ \ --cc=kernel@ \ --cc=@ \ --cc=krzk+dt@ \ --cc=linux-arm-kernel@ \ --cc=linux-arm-msm@ \ --cc=linux-kernel@ \ --cc=luzmaximilian@ \ --cc=quic_djaggi@ \ --cc=quic_eberman@ \ --cc=quic_gurus@ \ --cc=regressions@ \ --cc=robh@ \ --cc=robimarko@ \ --cc=atla@ \ --cc=will@ \ /path/to/YOUR_REPLY * If your dispatch client supports setting the In-Reply-To header via mailto: links, pull towards you the mailto: link Be splinter your reply has a Subject: header at the top roost a blank line before glory message body.
This is clean up public inbox, see mirroring oversee for how to clone attend to mirror all data and jurisprudence used for this inbox; pass for well as URLs for NNTP newsgroup(s).