mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH 0/2] MIPS: lantic: Fix "no prototype" warning
Date: Thu, 19 Oct 2023 10:51:38 +0200	[thread overview]
Message-ID: <ZTDuGnjB9kSrMxge@alpha.franken.de> (raw)
In-Reply-To: <20231010143406.974591-1-helgaas@kernel.org>

On Tue, Oct 10, 2023 at 09:34:04AM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
> 
> Fix a "no prototype" warning found by the kernel test robot.
> 
> Bjorn Helgaas (2):
>   MIPS: lantic: Fix pcibios_plat_dev_init() "no previous prototype"
>     warning
>   MIPS: lantic: Remove unnecessary include of <linux/of_irq.h>
> 
>  arch/mips/pci/fixup-lantiq.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

applied to mips-nextr. I've fixed lantic -> lantiq while applying.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2023-10-19  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 14:34 Bjorn Helgaas
2023-10-10 14:34 ` [PATCH 1/2] MIPS: lantic: Fix pcibios_plat_dev_init() "no previous " Bjorn Helgaas
2023-10-12  8:26   ` Philippe Mathieu-Daudé
2023-10-10 14:34 ` [PATCH 2/2] MIPS: lantic: Remove unnecessary include of <linux/of_irq.h> Bjorn Helgaas
2023-10-12  8:27   ` Philippe Mathieu-Daudé
2023-10-19  8:51 ` Thomas Bogendoerfer [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=ZTDuGnjB9kSrMxge@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.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

all inboxes | Powered by JetHome®