From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] pinctrl: ralink: rt305x: add missing include
Date: Wed, 30 Jun 2021 08:38:19 +0200 [thread overview]
Message-ID: <CAMhs-H8up-47e9T4uGxTfwiM1V=_ofok3-ZRbawFZKBVMnYk4A@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZJjuCMrxka5R2YLgcjwjjXCBEgDP5_+M7nxo5ZX6W4+A@mail.gmail.com>
On Wed, Jun 30, 2021 at 2:40 AM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Tue, Jun 29, 2021 at 4:34 PM Sergio Paracuellos
> <sergio.paracuellos@gmail.com> wrote:
>
> > Header 'rt305x.h' is ralink architecture dependent file where
> > other general definitions which are in 'ralink_regs.h' are
> > being used. This 'rt305x.h' is only being included in two
> > different files: 'rt305x.c' and 'pinctrl-rt305x.c'. When
> > file 'pinctrl-rt305x.c' is being compiled definitions in
> > 'ralink_regs.h' are need to build it properly. Hence, add
> > missing include 'ralink_regs.h' in 'pinctrl-rt305x.c'
> > source to avoid compilation problems.
> >
> > Fixes: 3a1b0ca5a83b ("pinctrl: ralink: move RT305X SoC pinmux config into a new 'pinctrl-rt305x.c' file")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
>
> Patch applied!
Thanks!
Best regards,
Sergio Paracuellos
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2021-06-30 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 14:34 [PATCH] pinctrl: ralink: rt305x: add missing include Sergio Paracuellos
2021-06-30 0:40 ` Linus Walleij
2021-06-30 6:38 ` Sergio Paracuellos [this message]
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='CAMhs-H8up-47e9T4uGxTfwiM1V=_ofok3-ZRbawFZKBVMnYk4A@mail.gmail.com' \
--to=sergio.paracuellos@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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).