From: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
To: Jonas Gorski <jonas.gorski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>,
Thomas Langer
<thomas.langer-th3ZBGNqt+7QT0dZR+AlfA@public.gmane.org>
Subject: Re: [RESEND PATCH V2 16/17] SPI: MIPS: lantiq: add FALCON spi driver
Date: Mon, 14 May 2012 20:45:20 +0200 [thread overview]
Message-ID: <4FB152C0.70400@openwrt.org> (raw)
In-Reply-To: <CAOiHx==N=au_PhR51tJjSZ8Em1tfZxv8gO7GJTD_MS=5dFAuEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 14/05/12 20:32, Jonas Gorski wrote:
> There was a patch accepted just a few days ago dropping the
> requirement for (un)prepare_transfer being populated :)
>
Hi,
this patch needs to flow via ralfs next tree, so i will keep this to
avoid merge order breaking the code. I will add it on my todo for RC1.
Will resend with your comments folded into the patch in a moment.
Thanks,
John
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
prev parent reply other threads:[~2012-05-14 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337017363-14424-1-git-send-email-blogic@openwrt.org>
2012-05-14 17:42 ` [RESEND PATCH V2 16/17] SPI: MIPS: lantiq: add FALCON spi driver John Crispin
[not found] ` <1337017363-14424-16-git-send-email-blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2012-05-14 18:32 ` Jonas Gorski
[not found] ` <CAOiHx==N=au_PhR51tJjSZ8Em1tfZxv8gO7GJTD_MS=5dFAuEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-14 18:45 ` John Crispin [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=4FB152C0.70400@openwrt.org \
--to=blogic-p3rkhjxn3npafugrpc6u6w@public.gmane.org \
--cc=jonas.gorski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=thomas.langer-th3ZBGNqt+7QT0dZR+AlfA@public.gmane.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).