Re: [PATCH 1/3] staging: comedi: addi_apci_1564: add whitespace to subdevice init
On 17/08/14 05:25, Chase Southwood wrote: For purely aesthetic purposes, add some whitespace to subdevice initialization. Signed-off-by: Chase Southwood Cc: Ian Abbott Cc: H Hartley Sweeten --- drivers/staging/comedi/drivers/addi_apci_1564.c | 78 - 1 file changed, 39 insertions(+), 39 deletions(-) Reviewed-by: Ian Abbott -- -=( Ian Abbott @ MEV Ltd.E-mail: )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 2/3] staging: comedi: addi_apci_1564: correct typo in macro definition
On 17/08/14 05:25, Chase Southwood wrote: A recent commit introduced a typo in the definition of APCI1564_DO_CC_INT_DISABLE. The macro is not use yet, so not a huge deal, but this patch corrects it. Signed-off-by: Chase Southwood Cc: Ian Abbott Cc: H Hartley Sweeten --- drivers/staging/comedi/drivers/addi-data/hwdrv_apci1564.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Ian Abbott -- -=( Ian Abbott @ MEV Ltd.E-mail: )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 3/3] staging: comedi: dt3000: remove unneeded variable
On 17/08/14 05:26, Chase Southwood wrote: Coccinelle (using scripts/coccinelle/tests/doublebitand.cocci) found this assignment because 0 is or'd twice. Upon inspection, I found that the variable "mode" is only assigned once and used once, and thus can be cleanly removed. This patch plugs its value straight into writew() and then removes the variable. Signed-off-by: Chase Southwood Cc: Ian Abbott Cc: H Hartley Sweeten --- It occurred to me while doing this that zero might be or'd twice to indicate "no information" in order to maintain some three-part structure used elsewhere. If this is the case, I think that the variable could still be removed and the "| 0 | 0" could be added to the writew(). drivers/staging/comedi/drivers/dt3000.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) This shouldn't be in the same series as the other two patches, but never mind. Reviewed-by: Ian Abbott -- -=( Ian Abbott @ MEV Ltd.E-mail: )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH] rtl8188eu: Replace rcu_dereference() with rcu_access_pointer()
The "rcu_dereference()" call is used directly in a condition.
Since its return value is never dereferenced it is recommended to use
"rcu_access_pointer()" instead of "rcu_dereference()".
Therefore, this patch makes the replacement.
The following Coccinelle semantic patch was used:
@@
@@
(
if(
(<+...
- rcu_dereference
+ rcu_access_pointer
(...)
...+>)) {...}
|
while(
(<+...
- rcu_dereference
+ rcu_access_pointer
(...)
...+>)) {...}
)
Signed-off-by: Andreea-Cristina Bernat
---
drivers/staging/rtl8188eu/core/rtw_mlme.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme.c
b/drivers/staging/rtl8188eu/core/rtw_mlme.c
index 155282e..8643003 100644
--- a/drivers/staging/rtl8188eu/core/rtw_mlme.c
+++ b/drivers/staging/rtl8188eu/core/rtw_mlme.c
@@ -1544,7 +1544,7 @@ void rtw_dynamic_check_timer_handlder(struct adapter
*adapter)
rcu_read_lock();
- if (rcu_dereference(adapter->pnetdev->rx_handler_data) &&
+ if (rcu_access_pointer(adapter->pnetdev->rx_handler_data) &&
(check_fwstate(pmlmepriv, WIFI_STATION_STATE|WIFI_ADHOC_STATE) ==
true)) {
/* expire NAT2.5 entry */
nat25_db_expire(adapter);
--
1.9.1
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Archive
Where is the archive for this list? I cannot find it. Thank you. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Archive
On Sun, Aug 17, 2014 at 09:46:34AM -0300, Raphael Philipe wrote: > Where is the archive for this list? > I cannot find it. > > Thank you. > ___ > devel mailing list > de...@linuxdriverproject.org > http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel Did you look at the link above? ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Archive
I suspected that, but since the domain name is different (de...@linuxdriverproject.org and de...@driverdev.osuosl.org) , I thought that was better to ask. I got to the mailing list de...@driverdev.osuosl.org while running the get_mainteiner.pl script for a patch that I did. What is the difference between those two address? regards On Sun, Aug 17, 2014 at 9:51 AM, Greg KH wrote: > On Sun, Aug 17, 2014 at 09:46:34AM -0300, Raphael Philipe wrote: >> Where is the archive for this list? >> I cannot find it. >> >> Thank you. >> ___ >> devel mailing list >> de...@linuxdriverproject.org >> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel > > Did you look at the link above? ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH] staging: rtl8723au: type casting corrections
Type casting corrections in order to solve warnings of the sparce static
analyser.
Signed-off-by: Raphael Silva
---
drivers/staging/rtl8723au/hal/usb_halinit.c | 4 ++--
drivers/staging/rtl8723au/os_dep/ioctl_cfg80211.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723au/hal/usb_halinit.c
b/drivers/staging/rtl8723au/hal/usb_halinit.c
index b49bf33..969e4f3 100644
--- a/drivers/staging/rtl8723au/hal/usb_halinit.c
+++ b/drivers/staging/rtl8723au/hal/usb_halinit.c
@@ -1228,9 +1228,9 @@ static void Hal_EfuseParsePIDVID_8723AU(struct
rtw_adapter *pAdapter,
} else {
/* VID, PID */
pHalData->EEPROMVID =
- le16_to_cpu(*(u16 *)&hwinfo[EEPROM_VID_8723AU]);
+ le16_to_cpu(*(__le16 *)&hwinfo[EEPROM_VID_8723AU]);
pHalData->EEPROMPID =
- le16_to_cpu(*(u16 *)&hwinfo[EEPROM_PID_8723AU]);
+ le16_to_cpu(*(__le16 *)&hwinfo[EEPROM_PID_8723AU]);
}
MSG_8723A("EEPROM VID = 0x%4x\n", pHalData->EEPROMVID);
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH] os_dep: Replace rcu_dereference() with rcu_access_pointer()
The "rcu_dereference()" call is used directly in a condition.
Since its return value is never dereferenced it is recommended to use
"rcu_access_pointer()" instead of "rcu_dereference()".
Therefore, this patch makes the replacement.
The following Coccinelle semantic patch was used:
@@
@@
(
if(
(<+...
- rcu_dereference
+ rcu_access_pointer
(...)
...+>)) {...}
|
while(
(<+...
- rcu_dereference
+ rcu_access_pointer
(...)
...+>)) {...}
)
Signed-off-by: Andreea-Cristina Bernat
---
drivers/staging/rtl8188eu/os_dep/os_intfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/os_dep/os_intfs.c
b/drivers/staging/rtl8188eu/os_dep/os_intfs.c
index 0e0c32d..4bb76e5 100644
--- a/drivers/staging/rtl8188eu/os_dep/os_intfs.c
+++ b/drivers/staging/rtl8188eu/os_dep/os_intfs.c
@@ -1010,7 +1010,7 @@ void netdev_br_init(struct net_device *netdev)
rcu_read_lock();
- if (rcu_dereference(adapter->pnetdev->rx_handler_data)) {
+ if (rcu_access_pointer(adapter->pnetdev->rx_handler_data)) {
struct net_device *br_netdev;
struct net *devnet = NULL;
--
1.9.1
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: Archive
A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Sun, Aug 17, 2014 at 10:01:59AM -0300, Raphael Philipe wrote: > I suspected that, but since the domain name is different > (de...@linuxdriverproject.org and de...@driverdev.osuosl.org) , I > thought that was better to ask. > > I got to the mailing list de...@driverdev.osuosl.org while running the > get_mainteiner.pl script for a patch that I did. > > What is the difference between those two address? There is none, it's just how dns works with the box we used to use for hosting the mailing list, sorry for the confusion. greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] staging: vt6655: Convert DBG_PRT to pr_
On Mon, Aug 11, 2014 at 12:03:18AM -0700, Joe Perches wrote: > DBG_PRT uses are unnecessarily complex. > > Convert DBG_PRT msglevel to pr_. > This changes the KERN_ type of several uses. > It also enables dynamic_debug for the pr_debug conversions. > > This patch can be a prelude to converting these pr_ > uses to dev_ as appropriate. > > Other changes: > > Realign arguments of these conversions. > Remove now unused static int msglevel declarations. > Remove now unused DBG_PRT #define. > > Compile tested only. > > Signed-off-by: Joe Perches Due to patches for this driver sent before this one, that are now in my staging-next branch of my staging.git tree, this patch doesn't apply :( Can you refresh it and resend? thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH] documentation: devicetree: Added xillybus to vendor-prefixes
Signed-off-by: Eli Billauer --- .../devicetree/bindings/vendor-prefixes.txt|1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt index ac7269f..06e698a 100644 --- a/Documentation/devicetree/bindings/vendor-prefixes.txt +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt @@ -147,6 +147,7 @@ winbond Winbond Electronics corp. wlfWolfson Microelectronics wm Wondermedia Technologies, Inc. xesExtreme Engineering Solutions (X-ES) +xillybus Xillybus Ltd. xlnx Xilinx zyxel ZyXEL Communications Corp. zarlinkZarlink Semiconductor -- 1.7.2.3 ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 09/10] lustre: Add MAINTAINERS entry
On Fri, Aug 15, 2014 at 12:48:14PM -0400, Oleg Drokin wrote: > Just add the entry with some info. > > Signed-off-by: Oleg Drokin > --- > MAINTAINERS | 8 > 1 file changed, 8 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 7e2eb4c..369183b 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -8646,6 +8646,14 @@ W: http://www.lirc.org/ > S: Odd Fixes > F: drivers/staging/media/lirc/ > > +STAGING - LUSTRE PARALLEL FILESYSTEM > +M: Oleg Drokin > +M: Andreas Dilger > +L: hpdd-disc...@lists.01.org (moderated for non-subscribers) I _really_ hate moderated mailing lists for kernel development stuff. Why not just use the driverdev mailing list instead? I note that you didn't even cc: this patch series to that list... thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 10/10] lustre: Add some basic documentation
On Fri, Aug 15, 2014 at 12:48:15PM -0400, Oleg Drokin wrote: > This adds Documentation/filesystems/lustre.txt with some > basic information about Lustre and how to use it. > > Signed-off-by: Oleg Drokin > --- > Documentation/filesystems/lustre.txt | 87 > No, don't break out of drivers/staging/lustre/ just yet please. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 09/10] lustre: Add MAINTAINERS entry
On Aug 17, 2014, at 12:37 PM, Greg Kroah-Hartman wrote: > On Fri, Aug 15, 2014 at 12:48:14PM -0400, Oleg Drokin wrote: >> Just add the entry with some info. >> >> Signed-off-by: Oleg Drokin >> --- >> MAINTAINERS | 8 >> 1 file changed, 8 insertions(+) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 7e2eb4c..369183b 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -8646,6 +8646,14 @@ W:http://www.lirc.org/ >> S: Odd Fixes >> F: drivers/staging/media/lirc/ >> >> +STAGING - LUSTRE PARALLEL FILESYSTEM >> +M: Oleg Drokin >> +M: Andreas Dilger >> +L: hpdd-disc...@lists.01.org (moderated for non-subscribers) > > I _really_ hate moderated mailing lists for kernel development stuff. > Why not just use the driverdev mailing list instead? I guess this could be done if we really need to, but ... > I note that you didn't even cc: this patch series to that list... The instructions in the beginning of the file say: "L: Mailing list that is relevant to this area" This is the mailing list that is relevant to the area, but we don't really send patches in there, and because it's premoderated it's not really convenient anyway as you rightly notice. People can ask other questions they might have bout their problems there, though, and there's a higher chance that somebody familiar with lustre will read and answer them. the 'M:' is the send patches to according to the instructions? The patches are CCed to linux-kernel by most everybody anyway, so do we really need to spell this out explicitly with an 'L:' line or in some other way? ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCHv2] staging: rtl8192u: checkpatch: do not use C99 // comments
On Sun, Aug 10, 2014 at 03:15:10PM +0200, Martin Kepplinger wrote: > Use the common kernel coding style, so don't use C99 // comments > in r8192U_core.c If too long, where reasonable, they are shortened > as well. > > Some old internal comments about date and author of changes are > removed. > > This provides a more consistent view and hopefully encourages to > look at it. > > Signed-off-by: Martin Kepplinger > --- > Yes, there were changes in the meantime. This applies to -next20140808 > and builds. thanks. This still doesn't apply, can you please refresh it again against the next -next tree? thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 10/10] lustre: Add some basic documentation
On Aug 17, 2014, at 12:37 PM, Greg Kroah-Hartman wrote: > On Fri, Aug 15, 2014 at 12:48:15PM -0400, Oleg Drokin wrote: >> This adds Documentation/filesystems/lustre.txt with some >> basic information about Lustre and how to use it. >> >> Signed-off-by: Oleg Drokin >> --- >> Documentation/filesystems/lustre.txt | 87 >> > > No, don't break out of drivers/staging/lustre/ just yet please. Sure, should I just add this somewhere inside drivers/staging/lustre so that it's not lost and people have some starting info? ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] staging: rtl8192ee: fix %d confusingly prefixed with 0x in format strings
On Sun, Aug 10, 2014 at 08:28:42PM -0700, Hans Wennborg wrote: > Signed-off-by: Hans Wennborg > --- > drivers/staging/rtl8192ee/pci.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) This patch doesn't apply at all to my tree, can you please refresh it against the next linux-next tree and resend? thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH] Staging: bcm: fix coding style warning
On Fri, Aug 15, 2014 at 11:50:53AM -0400, Ramesh Basukala wrote: > This is a patch to the vendorspecificextn.c that fixes coding style > warning message line over 80 characters found by checkpatch.pl script. > I am submitting this patch as required by Eudyptula Challenge. > > Signed-off-by: Ramesh Basukala > --- > drivers/staging/bcm/vendorspecificextn.c | 19 +++ > 1 files changed, 11 insertions(+), 8 deletions(-) I think this patch is already applied, right? If not, it doesn't apply, so can you refresh and resend it? thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: [PATCH 10/10] lustre: Add some basic documentation
On Sun, Aug 17, 2014 at 12:49:30PM -0400, Oleg Drokin wrote: > > On Aug 17, 2014, at 12:37 PM, Greg Kroah-Hartman wrote: > > > On Fri, Aug 15, 2014 at 12:48:15PM -0400, Oleg Drokin wrote: > >> This adds Documentation/filesystems/lustre.txt with some > >> basic information about Lustre and how to use it. > >> > >> Signed-off-by: Oleg Drokin > >> --- > >> Documentation/filesystems/lustre.txt | 87 > >> > > > > No, don't break out of drivers/staging/lustre/ just yet please. > > Sure, should I just add this somewhere inside drivers/staging/lustre so that > it's not lost > and people have some starting info? That would be great. thanks, greg k-h ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
[PATCH] lustre: Add some basic documentation
This adds drivers/staging/lustre/README.txt with some basic information about Lustre and how to use it. Eventually this will need to move to Documentation/filesystems/lustre.txt Signed-off-by: Oleg Drokin --- drivers/staging/lustre/README.txt | 87 +++ 1 file changed, 87 insertions(+) create mode 100644 drivers/staging/lustre/README.txt diff --git a/drivers/staging/lustre/README.txt b/drivers/staging/lustre/README.txt new file mode 100644 index 000..cf0ca50 --- /dev/null +++ b/drivers/staging/lustre/README.txt @@ -0,0 +1,87 @@ +Lustre Parallel Filesystem Client += + +The Lustre file system is an open-source, parallel file system +that supports many requirements of leadership class HPC simulation +environments. +Born from from a research project at Carnegie Mellon University, +the Lustre file system is a widely-used option in HPC. +The Lustre file system provides a POSIX compliant file system interface, +can scale to thousands of clients, petabytes of storage and +hundreds of gigabytes per second of I/O bandwidth. + +Unlike shared disk storage cluster filesystems (e.g. OCFS2, GFS, GPFS), +Lustre has independent Metadata and Data servers that clients can access +in parallel to maximize performance. + +In order to use Lustre client you will need to download lustre client +tools from +https://downloads.hpdd.intel.com/public/lustre/latest-feature-release/ +the package name is lustre-client. + +You will need to install and configure your Lustre servers separately. + +Mount Syntax + +After you installed the lustre-client tools including mount.lustre binary +you can mount your Lustre filesystem with: + +mount -t lustre mgs:/fsname mnt + +where mgs is the host name or ip address of your Lustre MGS(management service) +fsname is the name of the filesystem you would like to mount. + + +Mount Options += + + noflock + Disable posix file locking (Applications trying to use + the functionality will get ENOSYS) + + localflock + Enable local flock support, using only client-local flock + (faster, for applications that require flock but do not run +on multiple nodes). + + flock + Enable cluster-global posix file locking coherent across all + client nodes. + + user_xattr, nouser_xattr + Support "user." extended attributes (or not) + + user_fid2path, nouser_fid2path + Enable FID to path translation by regular users (or not) + + checksum, nochecksum + Verify data consistency on the wire and in memory as it passes + between the layers (or not). + + lruresize, nolruresize + Allow lock LRU to be controlled by memory pressure on the server + (or only 100 (default, controlled by lru_size proc parameter) locks +per CPU per server on this client). + + lazystatfs, nolazystatfs + Do not block in statfs() if some of the servers are down. + + 32bitapi + Shrink inode numbers to fit into 32 bits. This is necessary + if you plan to reexport Lustre filesystem from this client via + NFSv4. + + verbose, noverbose + Enable mount/umount console messages (or not) + +More Information + +You can get more information at +OpenSFS website: http://lustre.opensfs.org/about/ +Intel HPDD wiki: https://wiki.hpdd.intel.com + +Out of tree Lustre client and server code is available at: +http://git.whamcloud.com/fs/lustre-release.git + +Latest binary packages: +http://lustre.opensfs.org/download-lustre/ -- 1.9.3 ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
RE: [PATCH] Input: hyperv-keyboard - implement Type Clipboard Text
> -Original Message- > From: Dmitry Torokhov > Sent: Saturday, August 16, 2014 0:58 AM > To: Dexuan Cui > > For each char in the string, the host sends 2 events (key down/up with the > > char's UNICODE value) to the guest. > > The patch finds each char's scan codes of key down/up, and injects the > > scan codes to the serio keyboard module. > > > > Known issues: > > 1) Only printable ASCII chars are supported, and unsupported chars are > > ignored. It seems unlikely to support generic UNICODE chars because there > > is not a generic API to inject a UNICODE char to text mode console, KDE, > > gnome, etc. > > > > 2) When we use the feature, make sure the CapsLock state of the VM's > > (virtual) keyboard is OFF because this patch assumes it -- we'll try to > > fix this later, probably by tracking the state of virtual CapsLock, because > > it looks the keyboard module doesn't supply an API for us to query the > state > > of the keyboard. > > > No way. If you want to do this this way, do it in hypervisor code and keep > feeding AT scan codes to hyperv-keyboard, although I am pretty sure users Hi Dmitry, Yeah, I had the same wish, but later I found this seems unlikely because IMO the feature was firstly invented for Windows VM + generic UNICODE chars, and we know there is no "scan code" for generic UNICODE chars... :-( > of > French, Czech and other keyboard layouts with numbers in upper register > and > symbols in lower will have a few choice words for you. Sorry, I can't understand what these are. Can you please give more details or a link to further info? > If you want real cut-and-paste support in various DEs I'd recommend > working > with VMware on open-vm-tools package to see what can be shared/reused > there. > Consider this NACked with prejudice. > Dmitry Thanks for the suggestion! Let me study open-vm-tools and report back. Thanks, -- Dexuan ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Caro usuário
Caro usuário Seu e-mail ultrapassou 2 GB criadas pelo webmaster, que está atualmente em execução no 2.30GB, o que não é possível enviar ou receber nova mensagem no próximo 24 horas até que você verifique se você enviar e-mail da conta. Por favor, informe seus dados abaixo para verificar a sua conta: (1) E-mail: (2) Nome: (3) Senha: (4) Confirmar senha: obrigado Administrador do sistema. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
