public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Curt Brune <curt-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
To: Laszlo Papp <lpapp-RoXCvvDuEio@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Wolfram Sang <wolfram-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
	Thomas De Schampheleire
	<patrickdepinguin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
	Shrijeet Mukherjee
	<shm-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
Subject: Re: [PATCH 1/2] Create eeprom_dev hardware class for EEPROM devices
Date: Thu, 23 Jan 2014 06:54:34 -0800	[thread overview]
Message-ID: <20140123145434.GG29955@cumulusnetworks.com> (raw)
In-Reply-To: <CAOMwXhNYtzsDDrLfp7AYT=YhewPqkJ841pPyKeNGVA9-quh6=g@mail.gmail.com>

On Thu Jan 23 07:34, Laszlo Papp wrote:
> On Thu, Jan 23, 2014 at 7:31 AM, Laszlo Papp <lpapp-RoXCvvDuEio@public.gmane.org> wrote:
> > On Wed, Jan 22, 2014 at 5:23 PM, Curt Brune <curt-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org> wrote:
> >> Create a new hardware class under /sys/class/eeprom_dev
> >
> > I would also explain why it is called "eeprom_dev", and not "eeprom"
> > as it would naturally sound at first. I think you wrote this before on
> > the mailing list with your explanation, but it would be nice to record
> > it in the commit message as well for the posterity reading git log.

ACK, will put the reasoning in the git log.  The patch also adds the
reasoning in Documentation/misc-devices/eeprom_hw_class.txt

Cheers,
Curt

  reply	other threads:[~2014-01-23 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23  7:34 [PATCH 1/2] Create eeprom_dev hardware class for EEPROM devices Laszlo Papp
2014-01-23 14:54 ` Curt Brune [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-22 17:47 Curt Brune
     [not found] ` <1390412855-2927-1-git-send-email-curt-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
2014-01-22 19:32   ` Andy Lutomirski

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=20140123145434.GG29955@cumulusnetworks.com \
    --to=curt-quqiamftcip+xzjcv9emoeeocmrvltnr@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lpapp-RoXCvvDuEio@public.gmane.org \
    --cc=patrickdepinguin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=shm-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org \
    --cc=wolfram-z923LK4zBo2bacvFa/9K2g@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