Re: qcom: add LPAICP firmware for shikra platform

Venkata Kota <[email protected]> Mon, 22 Jun 2026 16:33:53 +0530
Newsgroups org.kernel.lore.linux-firmware
Message-ID <[email protected]>

On 6/22/2026 4:26 PM, Dmitry Baryshkov wrote:
> On Mon, Jun 22, 2026 at 03:14:19PM +0530, Venkata Kota wrote:
>>
>>
>> On 6/22/2026 2:03 PM, Dmitry Baryshkov wrote:
>>> On Mon, Jun 22, 2026 at 07:17:42AM +0530, Venkata Kota wrote:
>>>> The following changes since commit e7eb98afc667913acc533ab910c608bee7d08f25:
>>>>
>>>>     Merge branch 'robot/pr-0-1781081510' into 'main' (2026-06-10 10:48:39
>>>> +0000)
>>>
>>> This is the same and old commit.
>>>
>>>> The source branch is 36 commits behind the target branch
>>>
>>> And GL refuses to rebase it because of the conflicts.
>>>
>>>>
>>>> are available in the Git repository at:
>>>>
>>>>     https://git.codelinaro.org/clo/linux-kernel/linux-firmware.git
>>>> riscvfw-qli-shikra
>>>>
>>>> for you to fetch changes up to bcb6950bbf1df55f4588bc55abbd17051c4a1dc5:
>>>>
>>>>     qcom: add LPAICP firmware for shikra platform (2026-06-22 07:10:40 +0530)
>>>
>> There is no forking done here. The process is just the same for all the
>> other changes that we have pushed.
> 
> I didn't write anything about forking. I asked to _rebase_ on the repo's
> tip.
I understand that. Reference to forking does not make sense.

However, I was mentioning that we always run the following commands.

--git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

--cd linux-firmware/

--git config user.email "[email protected]"

--git checkout -b dsp-fw-00qcs83      (Create new branch with dsp-fw-*)

--git remote add clo-fw 
https://git.codelinaro.org/clo/linux-kernel/linux-firmware.git <which 
should push to the tip>
--git push clo-fw dsp-fw-00qcs83 (Branch)

--make changes, commit and push clo-fw
> 
>> I attempted to push on gitlab directly where i ran into the following error:
>> remote: GitLab: You are not allowed to push code to protected branches on
>> this project. This is the exact message here
>> To https://gitlab.com/vkasinat/linux-firmware.git
>> ! [remote rejected]   main -> main (pre-receive hook declined)
> 
> Which basically asks you, why you are pushing to the main branch
The idea was to try to push on the fork and raise a PR using gitlab -- 
similar to the way we run on github
> 
>> error: failed to push some refs to
>> 'https://gitlab.com/vkasinat/linux-firmware.git'
>