Messages in this thread | | | Date | Sun, 21 Mar 2021 13:06:29 -0700 (PDT) | From | Randy Dunlap <> | Subject | Re: [PATCH] x86/insn-eval: Few typo fixes |
| |
On Mon, 22 Mar 2021, Bhaskar Chowdhury wrote:
> > s/deterimine/determine/ > s/invalild/invalid/ > > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> --- > arch/x86/lib/insn-eval.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/lib/insn-eval.c b/arch/x86/lib/insn-eval.c > index bb0b3fe1e0a0..fdd9226863d3 100644 > --- a/arch/x86/lib/insn-eval.c > +++ b/arch/x86/lib/insn-eval.c > @@ -232,7 +232,7 @@ static int resolve_default_seg(struct insn *insn, struct pt_regs *regs, int off) > * resolve_seg_reg() - obtain segment register index > * @insn: Instruction with operands > * @regs: Register values as seen when entering kernel mode > - * @regoff: Operand offset, in pt_regs, used to deterimine segment register > + * @regoff: Operand offset, in pt_regs, used to determine segment register > * > * Determine the segment register associated with the operands and, if > * applicable, prefixes and the instruction pointed by @insn. > @@ -576,7 +576,7 @@ static int get_reg_offset_16(struct insn *insn, struct pt_regs *regs, > * If ModRM.mod is 0 and ModRM.rm is 110b, then we use displacement- > * only addressing. This means that no registers are involved in > * computing the effective address. Thus, ensure that the first > - * register offset is invalild. The second register offset is already > + * register offset is invalid. The second register offset is already > * invalid under the aforementioned conditions. > */ > if ((X86_MODRM_MOD(insn->modrm.value) == 0) && > -- > 2.31.0 > >
| |