From: Linus Walleij <linus.walleij@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: "Paul Cercueil" <paul@crapouillou.net>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Noralf Trønnes" <noralf@tronnes.org>
Subject: Re: [PATCH v5] drm/panel: db7430: Add driver for Samsung DB7430
Date: Fri, 11 Jun 2021 01:00:46 +0200 [thread overview]
Message-ID: <CACRpkdbNVB+k80a-iG53mhZ+DmZ2FokFiTG48QgGG-r89LmEyA@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=U9emGtV5Wj0jyAkHjLFrdnHOUhqqynFg-fvSVz2kibNQ@mail.gmail.com>
On Fri, Jun 11, 2021 at 12:42 AM Doug Anderson <dianders@chromium.org> wrote:
> On Thu, Jun 10, 2021 at 3:39 PM Linus Walleij <linus.walleij@linaro.org> wrote:
> > #define mipi_dbi_command(dbi, cmd, seq...) \
> > ({ \
> > const u8 d[] = { seq }; \
> > mipi_dbi_command_stackbuf(dbi, cmd, d, ARRAY_SIZE(d)); \
> > })
> >
> > I'll fix up the include and apply then we can think about
> > what to do with mipi_dbi_command().
>
> Are you sure that doesn't work? Isn't the return value of a macro the
> last expression? In this case the return value of
> mipi_dbi_command_stackbuf() should just flow through.
w00t I didn't know that.
And I like to think of the macro processor as essentially just
inserting the content of the macro at the cursor.
But arguably it *should* rather be fixed in this macro though?
It is used in the same way in all other drivers as well.
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-06-10 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 22:05 [PATCH v5] drm/panel: db7430: Add driver for Samsung DB7430 Linus Walleij
2021-06-10 22:30 ` Doug Anderson
2021-06-10 22:38 ` Linus Walleij
2021-06-10 22:42 ` Doug Anderson
2021-06-10 23:00 ` Linus Walleij [this message]
2021-06-10 23:05 ` Doug Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACRpkdbNVB+k80a-iG53mhZ+DmZ2FokFiTG48QgGG-r89LmEyA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=noralf@tronnes.org \
--cc=paul@crapouillou.net \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).