* Toshi Kani <toshi.k...@hp.com> wrote:

> When an MTRR entry is inclusive to a requested range, i.e.
> the start and end of the request are not within the MTRR
> entry range but the range contains the MTRR entry entirely,
> __mtrr_type_lookup() ignores such case because both
> start_state and end_state are set to zero.

'ignores such a case' or 'ignores such cases'.

> This patch fixes the issue by adding a new flag, inclusive,

s/inclusive/'inclusive'

Thanks,

        Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to