From: Joe Perches <joe@perches.com>
To: Paolo Pisati <p.pisati@gmail.com>
Cc: Alan Tull <atull@kernel.org>, Moritz Fischer <mdf@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support
Date: Thu, 22 Mar 2018 11:30:10 -0700 [thread overview]
Message-ID: <1521743410.7999.48.camel@perches.com> (raw)
In-Reply-To: <20180322172608.GA22179@harukaze>
On Thu, 2018-03-22 at 18:26 +0100, Paolo Pisati wrote:
> > It's frequently nicer to use a static function
> > for these enum -> string conversions like:
> >
> > static const char *get_err_string(unsigned long err)
> > {
> > switch (err) {
> > case ENOERR: return "No Error";
> > case EID: return "ID ERR";
> > case ECMD: return "CMD ERR";
> > [...]
> > }
> > return "default switch case";
> > }
>
> Ok - checkpatch complained when i put the "case ...: return ...;" on the same
> line as you did here, that is why i ended up with the ugly "case...: $string;
> break" all on different lines
checkpatch is brainless and stupid and if it
recommends stupid consistency over readability,
ignore it.
> > > + pr_debug("machxo2 status: 0x%08lX - done=%d, cfgena=%d, busy=%d, fail=%d, devver=%d, err=%s\n",
> > > + *status, test_bit(DONE, status), test_bit(ENAB, status),
> > > + test_bit(BUSY, status), test_bit(FAIL, status),
> > > + test_bit(DVER, status), ferr);
> >
> > So instead of ferr, this could use
> > get_err_string(*status)
> >
> > And please try to keep a consistent alignment for
> > indentation of multiple line statements
>
> I tried, but then checkpatch complained again about the indentation of the above block
> and i literally had to guess...
I think it only complained about the
2nd line that starts *status because it
doesn't align with the open parenthesis
of pr_debug
next prev parent reply other threads:[~2018-03-22 18:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 17:35 [PATCH 0/2 v7] Lattice MachXO2 Slave SPI FPGA Manager support Paolo Pisati
2018-03-21 17:35 ` [PATCH 1/2] dt: bindings: fpga: add lattice machxo2 slave spi binding description Paolo Pisati
2018-03-21 17:35 ` [PATCH 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support Paolo Pisati
2018-03-21 18:04 ` Joe Perches
2018-03-22 17:26 ` Paolo Pisati
2018-03-22 18:30 ` Joe Perches [this message]
2018-03-22 21:32 ` Alan Tull
2018-03-22 21:34 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2018-03-23 12:27 [PATCH 0/2 v8] Lattice MachXO2 Slave SPI FPGA Manager support Paolo Pisati
2018-03-23 12:27 ` [PATCH 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support Paolo Pisati
2018-03-28 16:26 ` Alan Tull
2018-03-28 20:03 ` Alan Tull
2018-03-29 14:33 ` Paolo Pisati
2018-03-16 15:54 [PATCH 0/2 v6] Lattice MachXO2 Slave SPI FPGA Manager support Paolo Pisati
2018-03-16 15:54 ` [PATCH 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support Paolo Pisati
2018-03-16 16:26 ` Moritz Fischer
2018-03-19 18:09 ` Paolo Pisati
2017-07-06 10:01 [PATCH v5 0/2] Lattice MachXO2 Slave SPI FPGA Manager support Paolo Pisati
[not found] ` <1499335270-6512-1-git-send-email-p.pisati-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-07-06 10:01 ` [PATCH 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support Paolo Pisati
2017-07-06 10:01 ` Paolo Pisati
2017-07-06 14:22 ` Moritz Fischer
2017-04-23 15:20 [PATCH 0/2] Lattice MachXO2 Passive SPI FPGA Manager support Paolo Pisati
[not found] ` <1492960845-342-1-git-send-email-p.pisati-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-23 15:20 ` [PATCH 2/2] fpga: lattice machxo2: Add Lattice MachXO2 support Paolo Pisati
2017-04-23 15:20 ` Paolo Pisati
[not found] ` <1492960845-342-3-git-send-email-p.pisati-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-25 15:59 ` Alan Tull
2017-04-25 15:59 ` Alan Tull
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=1521743410.7999.48.camel@perches.com \
--to=joe@perches.com \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mdf@kernel.org \
--cc=p.pisati@gmail.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.