| 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
| ||
|
Message-ID: <912ec82a1003300907o7edeb73bp92d56741cfee1064@mail.gmail.com> Date: Tue, 30 Mar 2010 19:07:18 +0300 From: Neshama Parhoti <pneshama@...il.com> To: linux-kernel@...r.kernel.org Subject: pr_* versus dev_* Which set of macros should I use in my driver ? pr_info, pr_err, etc... or dev_info, dev_err, etc. ? what are the advantages of the dev_* macros over the pr_* macros (why does it take the device pointer as an argument) ? obviously I don't have access to my device pointer in all my functions.. so pr_info is easier to use.. but if it's wanted, obviously I can arrange to have my device pointer accessible.. thank you ~pnesh -- 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/
Powered by blists - more mailing lists