From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [spi-devel-general] PATCH [1/1] SPI: AMBA_PL022: Limit TX FIFO fills based on current RX FIFO used
Date: Wed, 3 Feb 2010 23:15:46 +0100 [thread overview]
Message-ID: <63386a3d1002031415i4a407b44rfc6ace9ae5ab1c4f@mail.gmail.com> (raw)
In-Reply-To: <fa686aa41002030948g6359ef3o4c3a7b265490b93f@mail.gmail.com>
2010/2/3 Grant Likely <grant.likely@secretlab.ca>:
> I'm actively maintaining SPI now. ?In general, I'd prefer SPI patches
> to go through the SPI tree, unless there are commit ordering issues
> with arch code.
Sorry, will queue them in your tree next time, and thanks for picking
up SPI.
Yours,
Linus Walleij
prev parent reply other threads:[~2010-02-03 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <083DF309106F364B939360100EC290F805C4BF1E97@eu1rdcrdc1wx030.exi.nxp.com>
2010-01-22 12:56 ` [spi-devel-general] PATCH [1/1] SPI: AMBA_PL022: Limit TX FIFO fills based on current RX FIFO used Linus Walleij
2010-02-03 17:48 ` Grant Likely
2010-02-03 22:15 ` 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=63386a3d1002031415i4a407b44rfc6ace9ae5ab1c4f@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).