From: Emil Renner Berthing <kernel@esmil.dk>
To: Yash Shah <yash.shah@sifive.com>
Cc: sachin.ghadi@sifive.com, linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@sifive.com>,
paul.walmsley@sifive.com
Subject: Re: [RFC PATCH] spi: add driver for the SiFive SPI controller
Date: Wed, 13 Feb 2019 14:10:40 +0100 [thread overview]
Message-ID: <CANBLGcz4PJcChFxOsQYLKRy9SA11j1UsEN1pVpOBwfPQBmpM4A@mail.gmail.com> (raw)
In-Reply-To: <1550052211-21030-1-git-send-email-yash.shah@sifive.com>
Hi Yash,
On Wed, 13 Feb 2019 at 11:04, Yash Shah <yash.shah@sifive.com> wrote:
> I am working full time on Linux device drivers for SiFive.
> I have some bandwidth to work on this SPI driver.
> Do you mind if I take over this SPI driver from here on?
No, that's fine. You can pick it up from here:
https://github.com/esmil/linux/commit/870b04e85662a02ee1f6333e1d037c774ed4350e
That's with all of Mark's comments fixed, but the bindings doc
probably needs to be updated and split into a separate patch.
/Emil
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-02-13 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 14:27 [RFC PATCH] spi: add driver for the SiFive SPI controller Emil Renner Berthing
2018-11-12 14:27 ` Emil Renner Berthing
2018-11-13 18:35 ` Mark Brown
2018-11-13 18:35 ` Mark Brown
2018-11-13 19:48 ` Emil Renner Berthing
2018-11-13 19:48 ` Emil Renner Berthing
2018-11-13 22:38 ` Mark Brown
2018-11-13 22:38 ` Mark Brown
2019-02-13 10:03 ` Yash Shah
2019-02-13 13:10 ` Emil Renner Berthing [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=CANBLGcz4PJcChFxOsQYLKRy9SA11j1UsEN1pVpOBwfPQBmpM4A@mail.gmail.com \
--to=kernel@esmil.dk \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=sachin.ghadi@sifive.com \
--cc=yash.shah@sifive.com \
/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).