linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: martinwguy@gmail.com (Martin Guy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] spi: implemented driver for Cirrus EP93xx SPI controller
Date: Tue, 6 Apr 2010 22:28:53 +0100	[thread overview]
Message-ID: <x2r56d259a01004061428raffb32e9o1d42570c79c0ee56@mail.gmail.com> (raw)
In-Reply-To: <20100406181839.GA2685@gw.healthdatacare.com>

On 4/6/10, Mika Westerberg <mika.westerberg@iki.fi> wrote:
>  I only have one ep9302 board and 2 SPI devices

If you'd like one of the MMC-only boards to test on, I can ship it to
you - please provide smail mail address by private mail if that would
be welcome

>  > Lastly, what is the meaning of conditional operator(s) in
>  >         return t->bits_per_word ?: msg->spi->bits_per_word;
>  > It compiles, but it's the first time I've seen this construct in 27
>  > years of C programming. What is the "normal" syntax for this?
>
> It is an GCC extension:
>
>  http://gcc.gnu.org/onlinedocs/gcc-4.4.3/gcc/Conditionals.html#Conditionals
>
>  I've been using it once I saw it somewhere in the kernel source.

OK, I suggest we don't use "GNU extensions" if they can be avoided,
and program in C. The GCC monoculture is ending, thanks to llvm. and
those gnu-heads are not the most wise people on the planet. (OK, the
ANSI committe are worse, but.... :)

   M

  reply	other threads:[~2010-04-06 21:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 16:59 [PATCH v2 0/3] spi: driver for Cirrus EP93xx SPI controller Mika Westerberg
2010-03-18 17:00 ` [PATCH v2 1/3] spi: implemented " Mika Westerberg
2010-03-18 17:00   ` [PATCH v2 2/3] ep93xx: added chip revision reading function Mika Westerberg
2010-03-18 17:00     ` [PATCH v2 3/3] ep93xx: SPI driver platform support code Mika Westerberg
2010-03-18 17:27     ` [spi-devel-general] [PATCH v2 2/3] ep93xx: added chip revision reading function H Hartley Sweeten
2010-03-25  9:06       ` Mika Westerberg
2010-03-25 17:20         ` H Hartley Sweeten
2010-03-26 15:40           ` Martin Guy
2010-03-20 18:07     ` Martin Guy
2010-03-20 18:25       ` Daniel Mack
2010-03-20 18:40         ` Martin Guy
2010-03-20 19:31           ` H Hartley Sweeten
2010-03-20 19:48             ` Martin Guy
2010-03-20 18:31       ` Mika Westerberg
2010-03-20 19:42         ` H Hartley Sweeten
2010-03-21 18:45           ` Mika Westerberg
2010-03-25 13:49   ` [PATCH v2 1/3] spi: implemented driver for Cirrus EP93xx SPI controller Martin Guy
2010-03-25 18:43     ` Mika Westerberg
2010-04-01  0:15       ` Martin Guy
2010-04-01  3:00         ` Ryan Mallon
2010-04-01  6:26         ` Mika Westerberg
2010-04-06  5:44         ` Mika Westerberg
2010-04-06 12:50           ` Martin Guy
2010-04-06 18:18             ` Mika Westerberg
2010-04-06 21:28               ` Martin Guy [this message]
2010-04-09 17:56                 ` Martin Guy
2010-04-09 18:08                   ` Martin Guy
2010-04-10 15:54                   ` Mika Westerberg
2010-04-11 14:24                     ` Martin Guy
2010-04-12 10:03                     ` Martin Guy

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=x2r56d259a01004061428raffb32e9o1d42570c79c0ee56@mail.gmail.com \
    --to=martinwguy@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).