On Wed, 5 Jun 2019 16:30:10 -0400 "George G. Davis" <[email protected]> wrote:
> Fix a couple of s/poped/popped/ typos. > > Cc: Jiri Kosina <[email protected]> > Signed-off-by: George G. Davis <[email protected]> Acked-by: Steven Rostedt (VMware) <[email protected]> -- Steve > --- > Documentation/arm/mem_alignment | 2 +- > arch/x86/kernel/kprobes/core.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/arm/mem_alignment b/Documentation/arm/mem_alignment > index 6335fcacbba9..e110e2781039 100644 > --- a/Documentation/arm/mem_alignment > +++ b/Documentation/arm/mem_alignment > @@ -1,4 +1,4 @@ > -Too many problems poped up because of unnoticed misaligned memory access in > +Too many problems popped up because of unnoticed misaligned memory access in > kernel code lately. Therefore the alignment fixup is now unconditionally > configured in for SA11x0 based targets. According to Alan Cox, this is a > bad idea to configure it out, but Russell King has some good reasons for > diff --git a/arch/x86/kernel/kprobes/core.c b/arch/x86/kernel/kprobes/core.c > index 6afd8061dbae..d3243d93daf4 100644 > --- a/arch/x86/kernel/kprobes/core.c > +++ b/arch/x86/kernel/kprobes/core.c > @@ -813,7 +813,7 @@ __used __visible void *trampoline_handler(struct pt_regs > *regs) > continue; > /* > * Return probes must be pushed on this hash list correct > - * order (same as return order) so that it can be poped > + * order (same as return order) so that it can be popped > * correctly. However, if we find it is pushed it incorrect > * order, this means we find a function which should not be > * probed, because the wrong order entry is pushed on the
