All of lore.kernel.org
 help / color / mirror / Atom feed
From: Curt Brune <curt@cumulusnetworks.com>
To: Laszlo Papp <lpapp@kde.org>
Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>,
	gregkh@linuxfoundation.org,
	Shrijeet Mukherjee <shm@cumulusnetworks.com>,
	wolfram@the-dreams.de, linux-i2c@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Add at24 based EEPROMs to the eeprom_dev hardware class
Date: Thu, 23 Jan 2014 07:05:24 -0800	[thread overview]
Message-ID: <20140123150524.GH29955@cumulusnetworks.com> (raw)
In-Reply-To: <CAOMwXhMVgcVVWiUYbEgGcM+K5bZmKA3LO0=jZCEsyJak1TbTSA@mail.gmail.com>

On Thu Jan 23 07:44, Laszlo Papp wrote:
> On Wed, Jan 22, 2014 at 5:23 PM, Curt Brune <curt@cumulusnetworks.com> wrote:
> > During device instantiation have the at24 driver add the new device to
> > the eeprom_dev hardware class.  The functionality is enabled by
> > CONFIG_EEPROM_CLASS.
[snip]
> >  static void __exit at24_exit(void)
> >  {
> >         i2c_del_driver(&at24_driver);
> >  }
> >  module_exit(at24_exit);
> 
> Couldn't you use module_i2c_driver() instead of this?

I'm not sure what you mean.

Do you mean should the class registration/unregistration be put in
module_i2c_driver()?  That would not work as not all i2c devices are
eeproms.

> 
> >  MODULE_DESCRIPTION("Driver for most I2C EEPROMs");
> >  MODULE_AUTHOR("David Brownell and Wolfram Sang");
> 
> I would personally put your name in here if I were you, otherwise
> David and Wolfram might get contacted by some people instead of you
> (at least based on this).

Hmmm.   I don't know.  I didn't change the driver very much, just
added about 10 lines to a perfectly fine driver.  git-blame would
point right at me for anything to do with this patch.

> 
> PS.: Fixing the broken i2c mailing list typo, and updating Wolfram's
> address from the broken (obsolete?) version.

Thanks for fixing that.

Cheers,
Curt

  reply	other threads:[~2014-01-23 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23  7:44 [PATCH 2/2] Add at24 based EEPROMs to the eeprom_dev hardware class Laszlo Papp
2014-01-23  7:44 ` Laszlo Papp
2014-01-23 15:05 ` Curt Brune [this message]
     [not found]   ` <20140123150524.GH29955-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
2014-01-23 17:06     ` Laszlo Papp
2014-01-23 17:06       ` Laszlo Papp
2014-01-23 17:25 ` Wolfram Sang
2014-01-23 17:51   ` Laszlo Papp
     [not found]     ` <CAOMwXhPqnSNWtPMo7Qrr-O3qAqtjju7au7Mudckp7kN50yQW3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-23 18:15       ` Wolfram Sang
2014-01-23 18:15         ` Wolfram Sang
2014-01-23 19:10         ` Curt Brune
  -- strict thread matches above, loose matches on Subject: below --
2014-01-22 17:47 Curt Brune

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=20140123150524.GH29955@cumulusnetworks.com \
    --to=curt@cumulusnetworks.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpapp@kde.org \
    --cc=patrickdepinguin@gmail.com \
    --cc=shm@cumulusnetworks.com \
    --cc=wolfram@the-dreams.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.