[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZBveN3HT96/cktRI@ubun2204.myguest.virtualbox.org>
Date: Thu, 23 Mar 2023 10:35:59 +0530
From: Deepak R Varma <drv@...lo.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Julia Lawall <julia.lawall@...ia.fr>, Alex Elder <elder@...e.org>,
Menna Mahmoud <eng.mennamahmoud.mm@...il.com>,
outreachy@...ts.linux.dev, johan@...nel.org, elder@...nel.org,
linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [PATCH v2] staging: greybus: use inline function for macros
On Thu, Mar 23, 2023 at 05:58:02AM +0100, Greg KH wrote:
> Nice, that shows that it is the same both ways as the compiler version
> you are using is smart enough
>
> Which compiler and version is this? Does it work the same for all of
> the supported versions we have to support (i.e. really old gcc?)
>
> For the most part, sysfs files are not on any sort of "fast path" so a
Hello,
Is there a guideline/documentation on how to identify if a code is part of
fast/slow path?
> function call is fine, but as I mentioned before, sometimes we are
> forced to move calls to container_of() to container_of_const() and that
> can not be an inline function, but must remain a macro :(
>
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists