mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 21:17:44 +00:00
Everywhere: Clean up "the the" comment typos
This commit is contained in:
parent
b820b9b2ff
commit
daeaefad17
12 changed files with 15 additions and 15 deletions
|
@ -8,8 +8,8 @@
|
|||
will boot the AP from in real mode. This code also contains space for
|
||||
special variables that *must* remain here. When initializing the APIC,
|
||||
the code here gets copied to P0x00008000, the variables in here get
|
||||
populated and then the the boot of the APs will be triggered. Having
|
||||
the variables here allows us to access them from real mode. Also, the
|
||||
populated and then the boot of the APs will be triggered.
|
||||
Having the variables here allows us to access them from real mode. Also, the
|
||||
code here avoids the need for relocation entries.
|
||||
|
||||
Basically, the variables between apic_ap_start and end_apic_ap_start
|
||||
|
|
|
@ -19,8 +19,8 @@ code64_sel:
|
|||
will boot the AP from in real mode. This code also contains space for
|
||||
special variables that *must* remain here. When initializing the APIC,
|
||||
the code here gets copied to P0x00008000, the variables in here get
|
||||
populated and then the the boot of the APs will be triggered. Having
|
||||
the variables here allows us to access them from real mode. Also, the
|
||||
populated and then the boot of the APs will be triggered.
|
||||
Having the variables here allows us to access them from real mode. Also, the
|
||||
code here avoids the need for relocation entries.
|
||||
|
||||
Basically, the variables between apic_ap_start and end_apic_ap_start
|
||||
|
|
|
@ -284,8 +284,8 @@ ErrorOr<void> DisplayConnector::ioctl(OpenFileDescription&, unsigned request, Us
|
|||
SpinlockLocker locker(m_responsible_process_lock);
|
||||
auto process = m_responsible_process.strong_ref();
|
||||
// Note: If there's already a process being responsible, just return an error.
|
||||
// We could technically return 0 if the the requesting process is already
|
||||
// was set to be responsible for this DisplayConnector, but it servicing no
|
||||
// We could technically return 0 if the requesting process was already
|
||||
// set to be responsible for this DisplayConnector, but it services
|
||||
// no good purpose and should be considered a bug if this happens anyway.
|
||||
if (process)
|
||||
return Error::from_errno(EPERM);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue