core: Resolve misc cases of variable shadowing
Resolves shadowing warnings that aren't in a particularly large subsection of core. Brings us closer to turning -Wshadow into an error. All that remains now is for cases in the kernel (left untouched for now since a big change by bunnei is pending), and a few left over in the service code (will be tackled next).
This commit is contained in:
parent
c17a59b58e
commit
ebb64d5bf4
10 changed files with 27 additions and 25 deletions
|
@ -67,8 +67,8 @@ Freezer::~Freezer() {
|
|||
core_timing.UnscheduleEvent(event, 0);
|
||||
}
|
||||
|
||||
void Freezer::SetActive(bool active) {
|
||||
if (!this->active.exchange(active)) {
|
||||
void Freezer::SetActive(bool is_active) {
|
||||
if (!active.exchange(is_active)) {
|
||||
FillEntryReads();
|
||||
core_timing.ScheduleEvent(memory_freezer_ns, event);
|
||||
LOG_DEBUG(Common_Memory, "Memory freezer activated!");
|
||||
|
|
|
@ -43,7 +43,7 @@ public:
|
|||
~Freezer();
|
||||
|
||||
// Enables or disables the entire memory freezer.
|
||||
void SetActive(bool active);
|
||||
void SetActive(bool is_active);
|
||||
|
||||
// Returns whether or not the freezer is active.
|
||||
bool IsActive() const;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue