From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Steven Luo <steven@steven676.net>,
devel@driverdev.osuosl.org, fabs@goesec.de, tony@atomide.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>,
pavel@ucw.cz, pali.rohar@gmail.com, nico@ngolde.de
Subject: Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range
Date: Wed, 11 Dec 2013 11:57:04 +0200 [thread overview]
Message-ID: <52A836F0.9070500@gmail.com> (raw)
In-Reply-To: <20131211083359.GU28413@mwanda>
On 11.12.2013 10:33, Dan Carpenter wrote:
> On Wed, Dec 11, 2013 at 09:45:52AM +0200, Ivajlo Dimitrov wrote:
>> I can pick your changes and re-send the original patch with them
>> incorporated if there are no objections. Are you fine with that?
>>
> Do it on top of staging-next, don't redo the original.
>
> regards,
> dan carpenter
I don't see the original patch in the staging-next tree [0], how to
proceed? Isn't it better to resend the original patch with Steven's
changes included?
[0]
http://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/log/drivers/staging/tidspbridge?h=staging-next
Regards,
Ivo
next prev parent reply other threads:[~2013-12-11 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 20:00 [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range Ivaylo DImitrov
2013-12-07 23:49 ` Steven Luo
2013-12-08 13:01 ` Ivajlo Dimitrov
2013-12-11 7:45 ` Ivajlo Dimitrov
2013-12-11 8:33 ` Dan Carpenter
2013-12-11 9:57 ` Ivaylo Dimitrov [this message]
2013-12-11 10:27 ` Dan Carpenter
2013-12-12 1:57 ` Greg KH
2013-12-11 20:51 ` [PATCH] Staging: TIDSPBRIDGE: Fix mmap to map the correct region of physical memory Ivaylo DImitrov
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=52A836F0.9070500@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fabs@goesec.de \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@ngolde.de \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=steven@steven676.net \
--cc=tony@atomide.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