From: zhangyongle001@208suo.com
To: mpe@ellerman.id.au, npiggin@gmail.com, christophe.leroy@csgroup.eu
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH] floppy: ERROR: that open brace { should be on the previous line
Date: Thu, 20 Jul 2023 18:17:15 +0800 [thread overview]
Message-ID: <058c3448e220ee16bcb5e588271b685c@208suo.com> (raw)
Fix twoce occurrences of the checkpatch.pl error:
ERROR: that open brace { should be on the previous line
Signed-off-by: zhangyongle <zhangyongle001@208suo.com>
---
arch/powerpc/include/asm/floppy.h | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/include/asm/floppy.h
b/arch/powerpc/include/asm/floppy.h
index f8ce178b43b7..1ae67d2629be 100644
--- a/arch/powerpc/include/asm/floppy.h
+++ b/arch/powerpc/include/asm/floppy.h
@@ -163,16 +163,14 @@ static int hard_dma_setup(char *addr, unsigned
long size, int mode, int io)
return 0;
}
-static struct fd_dma_ops real_dma_ops =
-{
+static struct fd_dma_ops real_dma_ops = {
._disable_dma = disable_dma,
._free_dma = free_dma,
._get_dma_residue = get_dma_residue,
._dma_setup = hard_dma_setup
};
-static struct fd_dma_ops virt_dma_ops =
-{
+static struct fd_dma_ops virt_dma_ops = {
._disable_dma = vdma_disable_dma,
._free_dma = vdma_nop,
._get_dma_residue = vdma_get_dma_residue,
--
2.40.1
next reply other threads:[~2023-07-20 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 10:17 zhangyongle001 [this message]
2023-08-04 16:05 ` [PATCH] floppy: ERROR: that open brace { should be on the previous line Christophe Leroy
2023-08-07 0:36 ` Bagas Sanjaya
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=058c3448e220ee16bcb5e588271b685c@208suo.com \
--to=zhangyongle001@208suo.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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).