linux-kernel - Re: [PATCH v3] xHCI: Fixing xhci_readl definition and function call

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: <521E1292.5060709@gmail.com>
Date:	Wed, 28 Aug 2013 20:39:06 +0530
From:	Kumar Gaurav <kumargauravgupta3@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
CC:	sarah.a.sharp@...ux.intel.com, gregkh@...uxfoundation.org,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v3] xHCI: Fixing xhci_readl definition and function call

On Wednesday 28 August 2013 12:43 PM, Dan Carpenter wrote:
> On Mon, Aug 26, 2013 at 07:38:57AM +0530, Kumar Gaurav wrote:
>> This patch redefine function xhci_readl.xhci_readl function doesn't use xhci_hcd argument.
>> Hence there is no need of keeping it in the function arguments.
>>
>> Redefining this function breaks other functions which calls this function.
>> This phatch also correct those calls in xhci driver.
>>
>> Signed-off-by: Kumar Gaurav <kumargauravgupta3@...il.com>
>> ---
> Could you put a list of changes since v2 here?:
>
> v3:  blah blah changelog mostly.
>
> Also this doesn't apply for me against linux-next.
>
> regards,
> dan carpenter
>
There's no change from v2. I was sending the same patch again because 
the last one was lacking good description and i was told (or as i 
understood) that if I'm sending the same patch or patch for the same 
purpose as previous then i should increment version so i did.

I had developed this patch against linux-git, haven't tested that on 
linux-next as i haven't cloned  linux-next yet.

I've started cloning linux-next and as it's not applying on linux-next, 
I'll try it on linux-next (once i cloned it)  and will send again.

Regards
Kumar Gaurav
--
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/