linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Meerwald <pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org
Subject: [PATCH] i2c writing-clients document: mention module_i2c_driver()
Date: Wed, 18 Jan 2012 14:00:29 +0100	[thread overview]
Message-ID: <1326891629-8495-1-git-send-email-pmeerw@pmeerw.net> (raw)

From: Peter Meerwald <p.meerwald-12LT5diAjoA8TDmHOjzjNtBPR1lH4CV8@public.gmane.org>

---
 Documentation/i2c/writing-clients |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/Documentation/i2c/writing-clients b/Documentation/i2c/writing-clients
index 5aa5337..71248b2 100644
--- a/Documentation/i2c/writing-clients
+++ b/Documentation/i2c/writing-clients
@@ -266,6 +266,14 @@ be removed after kernel booting (or module loading) is completed.
 Likewise, functions marked by `__exit' are dropped by the compiler when
 the code is built into the kernel, as they would never be called.
 
+The module_i2c_driver() macro can be used to reduce above code.
+
+MODULE_AUTHOR("Frodo Looijaard <frodol-B0qZmFHriGg@public.gmane.org>"
+MODULE_DESCRIPTION("Driver for Barf Inc. Foo I2C devices");
+MODULE_LICENSE("GPL");
+
+module_i2c_driver(foo_driver);
+
 
 Power Management
 ================
-- 
1.7.4.1

             reply	other threads:[~2012-01-18 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 13:00 Peter Meerwald [this message]
     [not found] ` <1326891629-8495-1-git-send-email-pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>
2012-06-18 15:02   ` [PATCH] i2c writing-clients document: mention module_i2c_driver() Jean Delvare
     [not found]     ` <20120618170236.21b04fd5-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-06-18 16:41       ` Peter Meerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1326891629-8495-1-git-send-email-pmeerw@pmeerw.net \
    --to=pmeerw-jw+xmwgofnustnjn9+bgxg@public.gmane.org \
    --cc=lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).