From: Linus Walleij <linus.walleij@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: arch/arm/mach-ixp4xx/common-pci.c:143:5: warning: no previous prototype for 'ixp4xx_pci_write'
Date: Sat, 19 Feb 2022 01:41:53 +0100 [thread overview]
Message-ID: <CACRpkdbXDMorX6rSGyamKDRq_2ruEQG-J+N4cqiYedbQVF4dkQ@mail.gmail.com> (raw)
In-Reply-To: <202202172055.BVOB1ugQ-lkp@intel.com>
On Thu, Feb 17, 2022 at 1:24 PM kernel test robot <lkp@intel.com> wrote:
>
> Hi Linus,
>
> FYI, the error/warning still remains.
A pull request is pending to delete this entire file.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-02-19 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 12:23 arch/arm/mach-ixp4xx/common-pci.c:143:5: warning: no previous prototype for 'ixp4xx_pci_write' kernel test robot
2022-02-19 0:41 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-20 0:07 kernel test robot
2022-03-21 15:34 ` Linus Walleij
2022-01-15 20:32 kernel test robot
2022-01-29 1:17 ` Linus Walleij
2021-11-27 19:57 kernel test robot
2021-11-10 9:22 kernel test robot
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=CACRpkdbXDMorX6rSGyamKDRq_2ruEQG-J+N4cqiYedbQVF4dkQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=kbuild-all@lists.01.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).