Messages in this thread | | | Date | Mon, 24 Aug 2015 12:50:33 +0200 | From | Michal Hocko <> | Subject | Re: [PATCH 3/3] mm/memblock: fix memblock comment |
| |
On Sat 22-08-15 15:40:12, Yaowei Bai wrote: > 's/amd/and/'
Is this really worth it? It doesn't help grepability and just churns the history.
> > Signed-off-by: Yaowei Bai <bywxiaobai@163.com> > --- > include/linux/memblock.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/linux/memblock.h b/include/linux/memblock.h > index cc4b019..273aad7 100644 > --- a/include/linux/memblock.h > +++ b/include/linux/memblock.h > @@ -304,7 +304,7 @@ static inline void __init memblock_set_bottom_up(bool enable) {} > static inline bool memblock_bottom_up(void) { return false; } > #endif > > -/* Flags for memblock_alloc_base() amd __memblock_alloc_base() */ > +/* Flags for memblock_alloc_base() and __memblock_alloc_base() */ > #define MEMBLOCK_ALLOC_ANYWHERE (~(phys_addr_t)0) > #define MEMBLOCK_ALLOC_ACCESSIBLE 0 > > -- > 1.9.1 > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
-- Michal Hocko SUSE Labs
| |