On Mon, Sep 21, 2026 at 03:54:54PM +0200, Marek Vasut wrote: > On 9/21/26 3:30 PM, Francesco Dolcini wrote: > > Hello, > > > > On Mon, Sep 21, 2026 at 01:45:05PM +0800, Tom Hsieh wrote: > > > From: Tom Hsieh <[email protected]> > > > > > > The driver defines PHY_CTRL3_TXVREF_TUNE_MASK, > > > PHY_CTRL3_TXRISE_TUNE_MASK, PHY_CTRL3_TXPREEMP_TUNE_MASK, > > > PHY_CTRL3_COMPDISTUNE_MASK, PHY_CTRL3_TX_VBOOST_LEVEL_MASK, > > > PHY_CTRL4_PCS_TX_DEEMPH_3P5DB_MASK and > > > > [...] > > > > > Assisted-by: Claude:claude-opus-5 > > > > What is the policy on this in U-Boot? If we re-use the Linux kernel one > > it should be just LLM. > The author of the patch has to understand the code, and more importantly, be > legally responsible for the code they added. Therefore the author cannot be > purely the AI. > > For example if the AI generated the code based on some problematic or > closed-source content (do we surely know it did not?), the author has to be > legally responsible for any damages.
Yes, clear and I agree, to me this was granted. My comment was more if it was supposed to be just Assisted-by: LLM as the Linux kernel requires. Francesco
