Upon joining my current company, I renamed the team that I lead "infrastructure" for exactly this reason. That team was not a "devops" team except insofar as things were getting hucked over the wall and they necessitated some dev out of the ops folks.
My role here is arguably a more integrated one where we're working towards a devops-flavored culture, and the infrastructure team here is part of it: "we maintain the roads and set up the water mains and keep the power lines from falling down, but hooking up your house to power and electric and making sure it doesn't catch on fire--that's your responsibility."
I wish the insistance on devops not being a role, because of pedantics, would die. Yes we all know devops is a culture. But we also know its a role. Someone has to drive the culture. HR people are now calling themselves people operations, sales teams have sales operations aka salesops. Its not farfetched to have devevelor operations, aka devops as a role. Lets accept that both the role and culture exists, and move on.
My role here is arguably a more integrated one where we're working towards a devops-flavored culture, and the infrastructure team here is part of it: "we maintain the roads and set up the water mains and keep the power lines from falling down, but hooking up your house to power and electric and making sure it doesn't catch on fire--that's your responsibility."