From: Arun MURTHY <arun.murthy@stericsson.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>
Subject: RE: [PATCHv4 1/4] modem_shm: Add Modem Access Framework
Date: Thu, 11 Oct 2012 11:37:20 +0200 [thread overview]
Message-ID: <F45880696056844FA6A73F415B568C695B9B3E3D8A@EXDCVYMBSTM006.EQ1STM.local> (raw)
In-Reply-To: <20121009135918.GC5583@kroah.com>
> On Tue, Oct 09, 2012 at 07:37:02AM +0200, Arun MURTHY wrote:
> > Any further comments?
>
> I was waiting for you to address all of the previous ones with a new set of
> patches before burdening you with anything new :)
There are not any changes in the code, this review was more like just
explaining our platform, protocol, few terminology and design approach.
Thanks and Regards,
Arun R Murthy
------------------
next prev parent reply other threads:[~2012-10-11 9:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 8:05 [PATCHv4 0/4] modem_shm: U8500 SHaRed Memory driver(SHRM) Arun Murthy
2012-09-28 8:05 ` [PATCHv4 1/4] modem_shm: Add Modem Access Framework Arun Murthy
2012-09-28 16:00 ` Greg KH
2012-10-01 5:30 ` Arun MURTHY
2012-10-01 6:33 ` anish singh
2012-10-01 6:57 ` Arun MURTHY
2012-10-01 8:57 ` anish singh
2012-10-01 9:12 ` Arun MURTHY
2012-10-01 15:59 ` Greg KH
2012-10-03 3:54 ` Arun MURTHY
2012-10-03 4:17 ` anish singh
2012-10-03 4:31 ` Arun MURTHY
2012-10-03 15:17 ` Greg KH
2012-10-04 4:08 ` Arun MURTHY
2012-10-09 5:37 ` Arun MURTHY
2012-10-09 13:59 ` Greg KH
2012-10-11 9:37 ` Arun MURTHY [this message]
2012-10-11 11:01 ` Greg KH
2012-09-28 8:05 ` [PATCHv4 2/4] modem_shm: Register u8500 client for MAF Arun Murthy
2012-09-28 8:05 ` [PATCHv4 3/4] modem_shm: u8500-shm: U8500 Shared Memory Driver Arun Murthy
2012-09-28 8:05 ` [PATCHv4 4/4] Doc: Add u8500_shrm document Arun Murthy
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=F45880696056844FA6A73F415B568C695B9B3E3D8A@EXDCVYMBSTM006.EQ1STM.local \
--to=arun.murthy@stericsson.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).