From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Eric Anholt <eric@anholt.net>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] drm: pl111: Fix module autoloading
Date: Fri, 17 Apr 2020 22:09:59 +0200 [thread overview]
Message-ID: <CACRpkdbTO+fdW9EqEJQ=BUki-c4Nn6uUaD_TPf4Y2DyxM2TEsw@mail.gmail.com> (raw)
In-Reply-To: <20200409013947.12667-2-robh@kernel.org>
On Thu, Apr 9, 2020 at 3:39 AM Rob Herring <robh@kernel.org> wrote:
> Add a missing MODULE_DEVICE_TABLE entry to fix module autoloading.
>
> Cc: Eric Anholt <eric@anholt.net>
> Cc: dri-devel@lists.freedesktop.org
> Signed-off-by: Rob Herring <robh@kernel.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-17 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 1:39 [PATCH 0/3] drm: pl111: Fix module loading issues Rob Herring
2020-04-09 1:39 ` [PATCH 1/3] drm: pl111: Fix module autoloading Rob Herring
2020-04-09 14:12 ` Sam Ravnborg
2020-04-17 20:09 ` Linus Walleij [this message]
2020-04-09 1:39 ` [PATCH 2/3] drm: pl111: Simplify vexpress init Rob Herring
2020-04-09 14:16 ` Sam Ravnborg
2020-04-17 17:43 ` Rob Herring
2020-04-17 20:23 ` Linus Walleij
2020-04-09 1:39 ` [PATCH 3/3] drm: pl111: Move VExpress setup into versatile init Rob Herring
2020-04-09 14:34 ` Sam Ravnborg
2020-04-17 17:33 ` Rob Herring
2020-04-17 20:27 ` Linus Walleij
2020-04-19 17:12 ` Rob Herring
2020-04-17 20:28 ` [PATCH 0/3] drm: pl111: Fix module loading issues Linus Walleij
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='CACRpkdbTO+fdW9EqEJQ=BUki-c4Nn6uUaD_TPf4Y2DyxM2TEsw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
/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).