public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com
Subject: Re: [PATCH] i2c driver fixes for 2.6.1
Date: Wed, 21 Jan 2004 22:50:12 +0100	[thread overview]
Message-ID: <20040121225012.1addb5c7.khali@linux-fr.org> (raw)
In-Reply-To: <10745567661358@kroah.com>

> Also note that I slightly altered the condition to display the PCILynx
> comment. I think it's more logical that way. Without it, the user
> could get the message he/she needs I2C, go to enable it, come back and
> still not see the option.

For the records, please let it be noted that this change is *not* included
in the patch submitted by Greg.

That said, I still think it was a good idea. Not that it matters much to
me since I don't use that driver, but anyway... Who should I contact to
get it included?

Thanks.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

  parent reply	other threads:[~2004-01-21 21:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 23:57 [BK PATCH] i2c driver fixes for 2.6.1 Greg KH
2004-01-19 23:59 ` [PATCH] " Greg KH
2004-01-19 23:59   ` Greg KH
2004-01-19 23:59     ` Greg KH
2004-01-19 23:59       ` Greg KH
2004-01-19 23:59         ` Greg KH
2004-01-19 23:59           ` Greg KH
2004-01-19 23:59             ` Greg KH
2004-01-19 23:59               ` Greg KH
2004-01-19 23:59                 ` Greg KH
2004-01-19 23:59                   ` Greg KH
2004-01-19 23:59                     ` Greg KH
2004-01-19 23:59                       ` Greg KH
2004-01-19 23:59                         ` Greg KH
2004-01-19 23:59                           ` Greg KH
2004-01-19 23:59                             ` Greg KH
2004-01-19 23:59                               ` Greg KH
2004-01-19 23:59                                 ` Greg KH
2004-01-19 23:59                                   ` Greg KH
2004-01-19 23:59                                     ` Greg KH
2004-01-19 23:59                                       ` Greg KH
2004-01-19 23:59                                         ` Greg KH
2004-01-19 23:59                                           ` Greg KH
2004-01-19 23:59                                             ` Greg KH
2004-01-19 23:59                                               ` Greg KH
2004-01-19 23:59                                                 ` Greg KH
2004-01-19 23:59                                                   ` Greg KH
2004-01-19 23:59                                                     ` Greg KH
2004-01-19 23:59                                                       ` Greg KH
2004-01-19 23:59                                                         ` Greg KH
2004-01-21 21:50                                                 ` Jean Delvare [this message]
2004-01-21 23:56                                                   ` Greg KH
2004-01-31  8:56                                                     ` Jean Delvare
2004-01-31 15:23                                                       ` Greg KH
2004-01-20 22:03     ` Jean Delvare
2004-01-20 22:07       ` Greg KH
2004-01-21 20:47         ` Jean Delvare
2004-01-24  1:14           ` Greg KH

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=20040121225012.1addb5c7.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@Stimpy.netroedge.com \
    /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