qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jules Irenge <jbi.octave@gmail.com>
To: amarkovic@wavecomp.com
Cc: aurelien@aurel32.net, qemu-devel@nongnu.org, arikalo@wavecomp.com
Subject: [Qemu-devel] [PATCH 5/5] target/mips: wrap line into multiple lines to to fix checkpatch errors
Date: Wed,  3 Apr 2019 13:50:55 +0100	[thread overview]
Message-ID: <20190403125055.26564-6-jbi.octave@gmail.com> (raw)
In-Reply-To: <20190403125055.26564-1-jbi.octave@gmail.com>

Wrap line into multiple lines  to fix errors issued by checkpatch.pl tool
ERROR: line over 90 characters"
 within "target/mips/cpu.h" file.

Signed-off-by: Jules Irenge <jbi.octave@gmail.com>
---
 target/mips/cpu.h | 25 +++++++++++++++++++------
 1 file changed, 19 insertions(+), 6 deletions(-)

diff --git a/target/mips/cpu.h b/target/mips/cpu.h
index 238a67c405..56b0105574 100644
--- a/target/mips/cpu.h
+++ b/target/mips/cpu.h
@@ -72,15 +72,28 @@ struct CPUMIPSFPUContext {
 #define FCR31_FS 24
 #define FCR31_ABS2008 19
 #define FCR31_NAN2008 18
-#define SET_FP_COND(num, env)    do { ((env).fcr31) |= ((num) ? (1 << ((num) + 24)) : (1 << 23)); } while (0)
-#define CLEAR_FP_COND(num, env)   do { ((env).fcr31) &= ~((num) ? (1 << ((num) + 24)) : (1 << 23)); } while (0)
-#define GET_FP_COND(env)         ((((env).fcr31 >> 24) & 0xfe) | (((env).fcr31 >> 23) & 0x1))
+#define SET_FP_COND(num, env)    do { ((env).fcr31) |=  \
+                                        ((num) ? (1 << ((num) + 24)) : \
+                                         (1 << 23)); \
+                                    } while (0)
+#define CLEAR_FP_COND(num, env)   do { ((env).fcr31) &= \
+                                        ~((num) ? (1 << ((num) + 24)) : \
+                                         (1 << 23)); \
+                                     } while (0)
+#define GET_FP_COND(env)         ((((env).fcr31 >> 24) & 0xfe) | \
+                                  (((env).fcr31 >> 23) & 0x1))
 #define GET_FP_CAUSE(reg)        (((reg) >> 12) & 0x3f)
 #define GET_FP_ENABLE(reg)       (((reg) >>  7) & 0x1f)
 #define GET_FP_FLAGS(reg)        (((reg) >>  2) & 0x1f)
-#define SET_FP_CAUSE(reg, v)      do { (reg) = ((reg) & ~(0x3f << 12)) | ((v & 0x3f) << 12); } while (0)
-#define SET_FP_ENABLE(reg, v)     do { (reg) = ((reg) & ~(0x1f <<  7)) | ((v & 0x1f) << 7); } while (0)
-#define SET_FP_FLAGS(reg, v)      do { (reg) = ((reg) & ~(0x1f <<  2)) | ((v & 0x1f) << 2); } while (0)
+#define SET_FP_CAUSE(reg, v)      do { (reg) = ((reg) & ~(0x3f << 12)) | \
+                                       ((v & 0x3f) << 12); \
+                                     } while (0)
+#define SET_FP_ENABLE(reg, v)     do { (reg) = ((reg) & ~(0x1f <<  7)) | \
+                                               ((v & 0x1f) << 7);  \
+                                     } while (0)
+#define SET_FP_FLAGS(reg, v)      do { (reg) = ((reg) & ~(0x1f <<  2)) | \
+                                               ((v & 0x1f) << 2); \
+                                     } while (0)
 #define UPDATE_FP_FLAGS(reg, v)   do { (reg) |= ((v & 0x1f) << 2); } while (0)
 #define FP_INEXACT        1
 #define FP_UNDERFLOW      2
-- 
2.20.1

  parent reply	other threads:[~2019-04-03 12:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 12:50 [Qemu-devel] [PATCH 0/5] target/mips/cpu: errors and warnings coding style cleanup Jules Irenge
2019-04-03 12:50 ` [Qemu-devel] [PATCH 1/5] target/mips: add space to fix checkpatch errors Jules Irenge
2019-04-03 14:05   ` Aleksandar Markovic
2019-04-03 12:50 ` [Qemu-devel] [PATCH 2/5] target/mips: realign comments to fix checkpatch warnings Jules Irenge
2019-04-03 14:08   ` Aleksandar Markovic
2019-04-03 12:50 ` [Qemu-devel] [PATCH 3/5] target/mips: replace indentation with space to fix checkpatch errors Jules Irenge
2019-04-03 14:12   ` Aleksandar Markovic
2019-04-03 12:50 ` [Qemu-devel] [PATCH 4/5] target/mips: remove " Jules Irenge
2019-04-03 12:50 ` Jules Irenge [this message]
2019-04-03 13:17 ` [Qemu-devel] [PATCH 0/5] target/mips/cpu: errors and warnings coding style cleanup no-reply
2019-04-03 14:19 ` Aleksandar Markovic

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=20190403125055.26564-6-jbi.octave@gmail.com \
    --to=jbi.octave@gmail.com \
    --cc=amarkovic@wavecomp.com \
    --cc=arikalo@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.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).