All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>,
	netdev@vger.kernel.org, "Michael Wu" <flamingice@sourmilk.net>
Subject: Re: [PATCH] eeprom_93cx6: Add write support
Date: Thu, 21 Dec 2006 19:54:06 +0100	[thread overview]
Message-ID: <200612211954.08123.IvDoorn@gmail.com> (raw)
In-Reply-To: <a32f33a40612202322v349caae9j9078bb590239c999@mail.gmail.com>

Hi,

> > This patch addes support for writing to the eeprom,
> > this also moves some duplicate code into seperate functions.
> 
> John: Do you want me to merge this path with the eeprom merge patch,
> and move the patch that moves rt2x00 to use this eeprom module into a
> separate patch or all these 2 patches good enough?

I shouldn't write mails while tired. Let met explain myself. ;)
eeprom_93cx6 has now 2 patches pending:
 1 - move eeprom_93cx6 out of rt2x00 and into /lib
 2 - add write support for eeprom_93cx6

Should patch 1 be split into a patch to add eeprom_93cx6
to the /lib folder and a seperate patch to remove the module
from rt2x00?

And while redoing the patch, merge patch 2 with the patch to add
eeprom_93cx6 to /lib?

Ivo

      reply	other threads:[~2006-12-21 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 18:56 [PATCH] eeprom_93cx6: Add write support Ivo van Doorn
2006-12-13 19:06 ` Lennart Sorensen
2006-12-15 11:58   ` EEPROM infrastructure (was: [PATCH] eeprom_93cx6: Add write support) Ingo Oeser
2006-12-21  7:22   ` [PATCH] eeprom_93cx6: Add write support Ivo Van Doorn
2006-12-21 18:54     ` Ivo van Doorn [this message]

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=200612211954.08123.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=flamingice@sourmilk.net \
    --cc=linville@tuxdriver.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=netdev@vger.kernel.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 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.