tags 1040906 + moreinfo pending
thanks

Hello JiaLing,
Am Tue, Sep 19, 2023 at 06:03:27PM +0800 schrieb zhangjialing:
>     I've created a patch for this bug, but I'm uncertain about how
> hw->hw_cpuinfo should be handled. I've utilized the CPU Family and Model
> Name. Hope this patch might provide some assistance in addressing this bug.

Thank you very much for the patch, this is great help!

I reviewed your patch and it looks fine. So I intend to integrate it
and prepare a new release.

However, I have two questions before I can prepare the release:

1. What is the license of your patch? Is GPL 3+ fine?

2. Usually, I use "vendor" for hw->hw_cpuinfo, however, it looks like
   to me there is only one vendor? 

   In this case I think using "familiy" is fine. In the end, it is up
   to you porters to that architecture.

As I don't have access to this port, please check linuxinfo after
release.

I have another bug on my plate, but I would like to release sometime
in October.

Greetings

          Helge

-- 
      Dr. Helge Kreutzmann                     [email protected]
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: PGP signature

Reply via email to