Hi Jacobe, On Sun, Jun 23, 2024 at 02:21:39AM GMT, Jacobe Zang wrote: > > Any reason to strip info about origin of the patch, my SoB and > > present this work as your own? > > Sincerely express my apology to Ondrej. It's really my mistake. After getting > your permission if I could submit the patches. I jsut think if the author and > submitter is not the same person is strange so I changed it. Next tiem I will > avoid this mistake. Apologize again. > > > > I sincerely hope this is just a rookie mistake so please carefully read > the URL below: > > > https://www.kernel.org/doc/html/latest/process/submitting-patches.html > > Thanks for the guidance Arend. After reading the document I realized what a stupid mistake I made. > > BTW I have another question, except the SoB of the real author, should I also post the original link in commit message? I suggest keeping at least this part: > Partially copied from https://lore.kernel.org/all/c7b331edd65b66521a6605177d654e55051568a3.camel@xxxxxxxxxxx/ > > (No Signed-off-by provided in the email. The code looks like some > data copied probably from a vendor driver and adapted for the upstream > one.) I'm not the complete author of the patch either. I just figured out why just adding device/chip IDs was not enough compared to what Marcel Ziswiler tried and expanded the patch from his email, to make it work. People using baords with AP6275P (eg. I did my debugging on QuartzPro64) will also be interested in how to get the firmware for AP6275P, and there are some hints for that in the above link, too. (FW filename that is in the patch for the driver doesn't match FW name as distributed by eg. SparkLAN, which makes it harder to find it just based on FW name from the code) Although it would be nice to have the firmware available in linux-firmware. Kind regards, o. > --- > Best Regards > Jacobe
