From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] SPI: fix up some PL022 confusion
Date: Mon, 17 May 2010 08:21:45 +0200 [thread overview]
Message-ID: <AANLkTinsCSb_k3y8iqk4nJ5793SNeg-uBA7Ac95nuNsu@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil25g0DEafaicc_fShwz9gpF8Dl9NgyG6E0wu-r@mail.gmail.com>
2010/5/11 Linus Walleij <linus.ml.walleij@gmail.com>:
> 2010/5/5 Linus Walleij <linus.walleij@stericsson.com>:
>
>> The PL022 SPI driver did not cleanly separate between the
>> original unmodified ARM version and the ST Microelectronics
>> versions. Split this more cleanly and fix some whitespace
>> moaning from checkpatch at the same time.
>
> Grant/David have you had time to look at these two PL022
> patches?
Still travelling? I'm just worrying that if I have to make any updates
for the merge tree I need some slack... sorry for hammering.
Yours,
Linus Walleij
prev parent reply other threads:[~2010-05-17 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 9:28 [PATCH] SPI: fix up some PL022 confusion Linus Walleij
2010-05-11 5:59 ` Linus Walleij
2010-05-17 6:21 ` Linus Walleij [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=AANLkTinsCSb_k3y8iqk4nJ5793SNeg-uBA7Ac95nuNsu@mail.gmail.com \
--to=linus.ml.walleij@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).