[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190410230933.7d1138b3@oasis.local.home>
Date: Wed, 10 Apr 2019 23:09:33 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
Andy Lutomirski <luto@...nel.org>,
Alexander Potapenko <glider@...gle.com>,
iommu@...ts.linux-foundation.org,
Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [RFC patch 28/41] dma/debug: Simplify stracktrace retrieval
On Wed, 10 Apr 2019 22:02:01 -0500
Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> > #ifdef CONFIG_STACKTRACE
> > - struct stack_trace stacktrace;
> > - unsigned long st_entries[DMA_DEBUG_STACKTRACE_ENTRIES];
> > + unsigned int st_len;
> > + unsigned long st_entries[DMA_DEBUG_STACKTRACE_ENTRIES];
>
> nit: st_entries isn't very readable. Thanks to the magic of compilers,
> the characters are free, so why not call them "stacktrace_entries" and
> "stacktrace_len".
But doesn't that slow down the time it takes to compile?
/me runs...
-- Steve
Powered by blists - more mailing lists