Re: QCA: Add Bluetooth firmware for QCC2072 uart interface
Vivek Sahu <[email protected]>
| Newsgroups | org.kernel.lore.linux-firmware |
|---|---|
| Message-ID | <[email protected]> |
On 1/12/2026 12:46 PM, Dmitry Baryshkov wrote: > On Mon, 12 Jan 2026 at 09:16, Vivek Sahu <[email protected]> wrote: >> >> On 1/9/2026 4:46 PM, Dmitry Baryshkov wrote: >>> On Fri, Jan 09, 2026 at 12:24:58PM +0530, Vivek Sahu wrote: >>>> On 1/8/2026 6:18 PM, Dmitry Baryshkov wrote: >>>>> On Thu, Jan 08, 2026 at 02:33:22PM +0530, Vivek Sahu wrote: >>>>>> Hi linux-firmware maintainers, >>>>>> >>>>>> Here's a pull request for btqca bluetooth driver. Please let me know if you >>>>>> have any problems. >>>>>> >>>>>> >>>>>> The following changes since commit e272e0d1edce58496c3917f7422b9531daeb0535: >>>>>> >>>>>> Merge branch 'robot/pr-0-1767725013' into 'main' (2026-01-06 19:05:06 >>>>>> +0000) >>>>>> >>>>>> are available in the Git repository at: >>>>>> >>>>>> https://github.com/vivesahu-huboss/Cologne_FW_Upstream.git HEAD >>>>>> >>>>>> for you to fetch changes up to 5fce4edd5a84b09c670918cfcaa0705eaf1c2b60: >>>>>> >>>>>> QCA: Add Bluetooth firmware for QCC2072 uart interface This commit will >>>>>> add required Bluetooth firmware files for QCC2072 uart interface. >>>>>> (2026-01-08 13:20:45 +0530) >>>>>> >>>>>> ---------------------------------------------------------------- >>>>>> Vivek Kumar Sahu (1): >>>>>> QCA: Add Bluetooth firmware for QCC2072 uart interface This commit >>>>>> will add required Bluetooth firmware files for QCC2072 uart interface. >>>>> Oh. And your git setup is broken. How did you end up with the SoB not >>>>> matching the Author of the commit (yes, I really want to know, how). >>>> my gitconfig file was not updated with oss mail id leading to this issue. >>> Are you writing the SoB manually? I'm asking because `git commit -s` >>> would use the same Git config for both Author and SoB. >> Yes, I was writing it manually. > Why? `git commit -s` does that for you (add an alias, if that's too > long to type). Yes, that is the right way of doing it. I'll follow that next time. >>>> I'll update it in next commit. >>>> > >