From: Adrian McMenamin <lkmladrian@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Adrian McMenamin <adrian@newgolddream.dyndns.info>,
Paul Mundt <lethal@users.sourceforge.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input <linux-input@vger.kernel.org>,
linux-sh <linux-sh@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sh: maple: Update the maple bus driver to support block reads and writes
Date: Sat, 14 Feb 2009 22:09:27 +0000 [thread overview]
Message-ID: <8b67d60902141409q39a79e67va422846f685f969d@mail.gmail.com> (raw)
In-Reply-To: <20090214215919.GA24052@kroah.com>
2009/2/14 Greg KH <greg@kroah.com>:
> On Sat, Feb 14, 2009 at 08:05:48PM +0000, Adrian McMenamin wrote:
>> Greg,
>>
>> This patch updates the maple bus to support asynchronous block reads and
>> writes as well as generally improving the quality of the code and
>> supporting concurrency (all needed to support the Dreamcast visual
>> memory unit - a driver will also be posted for that).
>>
>> I have posted versions of this before but am here following the patch
>> grouping suggested and have also tested this code and unlike earlier
>> versions it shows no signs of suffering from race conditions - so I hope
>> you will be happy to queue it for inclusion.
>
> Looks good to me, but shouldn't this go through the sh maintainers
> instead? This is their area, right?
As it's a change to a bus I thought you were the maintainer?
next prev parent reply other threads:[~2009-02-14 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 20:05 [PATCH] sh: maple: Update the maple bus driver to support block reads and writes Adrian McMenamin
2009-02-14 20:16 ` Adrian McMenamin
2009-02-14 20:26 ` [PATCH] mtd: sh: maple: Support the Dreamcast visual memory unit as a flash mapping Adrian McMenamin
2009-02-27 7:08 ` Paul Mundt
2009-02-27 7:06 ` [PATCH] sh: maple: Update the maple bus driver to support block reads and writes Paul Mundt
2009-02-14 21:59 ` Greg KH
2009-02-14 22:09 ` Adrian McMenamin [this message]
2009-02-14 22:27 ` Greg KH
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=8b67d60902141409q39a79e67va422846f685f969d@mail.gmail.com \
--to=lkmladrian@gmail.com \
--cc=adrian@newgolddream.dyndns.info \
--cc=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=lethal@users.sourceforge.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.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).