From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: linux-mips@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V2] MIPS: PCI: Remove leading space in info message, rename pci
Date: Tue, 5 Jul 2022 12:22:37 +0200 [thread overview]
Message-ID: <20220705102237.GD9951@alpha.franken.de> (raw)
In-Reply-To: <20220620115549.39177-1-colin.i.king@gmail.com>
On Mon, Jun 20, 2022 at 12:55:49PM +0100, Colin Ian King wrote:
> There is an info message with an extraneous leading space. Remove it.
> Also rename pci to PCI.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> V2: make pci uppercase
> ---
> arch/mips/pci/fixup-lemote2f.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/pci/fixup-lemote2f.c b/arch/mips/pci/fixup-lemote2f.c
> index 632ff2daa338..790d674cd80a 100644
> --- a/arch/mips/pci/fixup-lemote2f.c
> +++ b/arch/mips/pci/fixup-lemote2f.c
> @@ -80,7 +80,7 @@ int pcibios_map_irq(const struct pci_dev *dev, u8 slot, u8 pin)
> }
> return dev->irq;
> } else {
> - printk(KERN_INFO " strange pci slot number.\n");
> + printk(KERN_INFO "strange PCI slot number.\n");
> return 0;
> }
> }
> --
> 2.35.3
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-07-05 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 11:55 [PATCH][V2] MIPS: PCI: Remove leading space in info message, rename pci Colin Ian King
2022-07-05 10:22 ` 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=20220705102237.GD9951@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.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).