PCIe recovery mechanism

Hello, I was wondering if there is any way to recover from FW crash in case of WLAN PCie cards- say we power off card and power on. This would enable hotplug to detect it again and driver's probe routine would do redownload of FW and device is alive again. 1. I went through PCI bus driver

Re: Paging - can i know the last owner(pid) of a given page?

hi : the struct of mm_struct which task_struct involve it may be right. http://lxr.oss.org.cn/source/include/linux/mm_types.h?v=3.17#L345 2015-01-08 17:09 GMT+08:00 manty kuma mantyk...@gmail.com: Dear friends, I have a very simple question related to pages. Suppose, I have a kernel

Re: PCIe recovery mechanism

On Fri, Jan 09, 2015 at 10:19:15AM +0530, Avinash Patil wrote: Hello, I was wondering if there is any way to recover from FW crash in case of WLAN PCie cards- say we power off card and power on. This would enable hotplug to detect it again and driver's probe routine would do redownload of

Re: Submitted a first patch and no reply

Hi, Actually on the website it's return that Pick a warning, and try to fix it. For your first patch, only pick one warning. In the future you can group multiple changes into one patch, but only if you follow the PatchPhilosophy http://kernelnewbies.org/PatchPhilosophy of breaking each patch

Re: Submitted a first patch and no reply

On Thu, 2015-01-08 at 15:49 -0500, valdis.kletni...@vt.edu wrote: On Thu, 08 Jan 2015 12:37:15 -0800, shirish gajera said: That's hwy I just fix one warning. That means don't fix a warning about indentation *and* a warning about trailing blanks in the same patch. Also, if you're

[PATCH] checkpatch: Allow comments in macros tested for single statements

Convert all the comments to spaces before testing for single statement macros. Reported-by: Valdis Kletnieks valdis.kletni...@vt.edu Signed-off-by: Joe Perches j...@perches.com --- It's interesting that the warning only popped on the one case where the /* looping version */ is on a separate

Re: Submitted a first patch and no reply

On Thu, 08 Jan 2015 12:37:15 -0800, shirish gajera said: That's hwy I just fix one warning. That means don't fix a warning about indentation *and* a warning about trailing blanks in the same patch. Also, if you're fixing a style issue, you should actually *review* the code, and make sure you

Re: Submitted a first patch and no reply

I will make necessary and try to re- submit the patch. On Thu, Jan 8, 2015 at 1:14 PM, Joe Perches j...@perches.com wrote: On Thu, 2015-01-08 at 15:49 -0500, valdis.kletni...@vt.edu wrote: On Thu, 08 Jan 2015 12:37:15 -0800, shirish gajera said: That's hwy I just fix one warning.

Submitted a first patch and no reply

Hi, I have submitted my first patch on 12/30/2014 and I have not received any reply for next step like error or merge ect. I send the email to person that get_maintainer.pl script tells me to send. Please guide whom should I reached for this. Below is the email - This patch fixes the

Re: Submitted a first patch and no reply

On Thu, 08 Jan 2015 12:00:07 -0800, shirish gajera said: WARNING: Single statement macros should not use a do {} while (0) loop I have added single statement in curly braces, because it was giving me WARNING: macros should not use a trailing semicolon. Signed-off-by: Shirish Gajera