kern: fix incorrect format in device_if.m

[markj]

The tabbed indentation is correct. If anything, the other methods should be converted to use the correct style.

(Long long ago, subr_bus.c was indented using 4 spaces. That was fixed in commit 38c490a10f71c784fdbf2b8d663a83b78c23ced4, but this file was not updated.)

[aokblast]

Fix other

[aokblast]

In D51755#1182361, @markj wrote:

The tabbed indentation is correct. If anything, the other methods should be converted to use the correct style.

(Long long ago, subr_bus.c was indented using 4 spaces. That was fixed in commit 38c490a10f71c784fdbf2b8d663a83b78c23ced4, but this file was not updated.)

I thought it is some special format rule for .m files. Fix it now.

[markj]

Approved

You can add this commit to .git-blame-ignore-revs as a follow-up.

sys/kern/device_if.m

70

Since you're fixing style anyway

[lwhsu]

You can also put "no functional change." in the comment message if you want.

[mhorne]

sys/kern/device_if.m

52

What about return braces?

[aokblast]

In D51755#1182376, @markj wrote:

Approved

You can add this commit to .git-blame-ignore-revs as a follow-up.

Should I create a separate patch for this? I can not add it into the same patch since it changes git hash or I can just push it.

[markj]

In D51755#1183142, @aokblast wrote:

In D51755#1182376, @markj wrote:

Approved

You can add this commit to .git-blame-ignore-revs as a follow-up.

Should I create a separate patch for this? I can not add it into the same patch since it changes git hash or I can just push it.

Yes, it needs to be a separate patch. You can just go ahead and push that as a follow-up change.