linux-kernel - Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52A836F0.9070500@gmail.com>
Date:	Wed, 11 Dec 2013 11:57:04 +0200
From:	Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
CC:	Steven Luo <steven@...ven676.net>, devel@...verdev.osuosl.org,
	fabs@...sec.de, tony@...mide.com, gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org, Joe Perches <joe@...ches.com>,
	pavel@....cz, pali.rohar@...il.com, nico@...lde.de
Subject: Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing
 instead of remap_pfn_range

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/