This is a cool idea and it will help in some cases.
In the past, we had some chip definitions which conflicted with such an approach, though: There was a generic chip entry for one family of chips, and a specific entry for one chip of the family. If we merge this patch, we either need a commit hook checking all possible chip variants for duplicate entries, or a builtin self test which checks for duplicates.

Even better would be not having to hardcode the flash chip name in scripts. What made you hardcode the chip name in the first place, and can we fix that?

View Change

To view, visit change 37723. To unsubscribe, or for help writing mail filters, visit settings.