Skip to content
Snippets Groups Projects
Commit 11638eb1 authored by Bas Stottelaar's avatar Bas Stottelaar
Browse files

cpu: efm32: fix typo in cpus.txt

parent e0921443
No related branches found
No related tags found
No related merge requests found
# This file is automatically generated, and should not be changed. There is # This file is automatically generated, and should not be changed. There is
# propbably little reason to edit this file anyway, since it should already # probably little reason to edit this file anyway, since it should already
# contain all information for the EFM32GG family of CPUs. # contain all information for the EFM32GG family of CPUs.
# The intended usage is to grep for the exact model name, and split by spaces # The intended usage is to grep for the exact model name, and split by spaces
......
# This file is automatically generated, and should not be changed. There is # This file is automatically generated, and should not be changed. There is
# propbably little reason to edit this file anyway, since it should already # probably little reason to edit this file anyway, since it should already
# contain all information for the EFM32LG family of CPUs. # contain all information for the EFM32LG family of CPUs.
# The intended usage is to grep for the exact model name, and split by spaces # The intended usage is to grep for the exact model name, and split by spaces
......
# This file is automatically generated, and should not be changed. There is # This file is automatically generated, and should not be changed. There is
# propbably little reason to edit this file anyway, since it should already # probably little reason to edit this file anyway, since it should already
# contain all information for the EFR32MG1P family of CPUs. # contain all information for the EFR32MG1P family of CPUs.
# The intended usage is to grep for the exact model name, and split by spaces # The intended usage is to grep for the exact model name, and split by spaces
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment