What is correct will depend on your use for the data, but there are some things to watch out for with concatenating these values to a string. For example, if you want to find all rows that have "Honda" ever (and you probably will), this might be a bad way to store the data.
I would probably make some extra tables: car_make, car_make_group, and car_make_to_group . I'd put
car_make (make_id, make_desc)
------------------
1, "Toyota"
2, "Honda"
3, "Nissan"
I would number my groups like a bit flag enum, but that's not really important..it is just a way to assign numbers to groups in a way that doesn't collide. It also has the property that everything is additive (group2 + group4 = group6). I always provide an association table, though.
car_make_group (make_group_id, make_group_desc)
------------------
1, "Toyota"
2, "Honda"
3, "Toyota, Honda"
4, "Nissan"
5, "Toyota, Nissan"
6, "Honda, Nissan"
7, "Toyota, Honda, Nissan"
Finally, I would make an association table to help with queries:
car_makes_to_group (make_id, make_group_id)
------------------
1, 1
1, 3
1, 5
1, 7
2, 2
2, 3
2, 6
2, 7
3, 4
3, 5
3, 6
3, 7
Using multiple tables will allow you some flexibility for future changes. For example, you could realize later that you want to use JSON and change the make_group_desc to hold the JSON string instead of the comma-separated string.
You'll be able to run an ad-hoc query where you find every row that includes "Toyota" also:
Select m.make_id, m.make_desc, g.make_group_id, g.make_group_desc
FROM car_make_to_group t
INNER JOIN car_make_group g
ON (t.make_group_id = g.make_group_id)
INNER JOIN car_make m
ON (t.make_id = m.make_id)
WHERE m.make_desc = "Toyota"