From: gregkh@suse.de (Greg KH)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>,
linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Date: Thu, 19 May 2005 06:25:52 +0000 [thread overview]
Message-ID: <20050419043938.GA23724@kroah.com> (raw)
Alright, let's try some small i2c and w1 patches...
Could you merge with:
kernel.org/pub/scm/linux/kernel/git/gregkh/i2c-2.6.git/
It contains 4 small patches, 2 i2c and 2 w1 bugfixes, diffstat is
below, I'll figure out how to send the individual patches later.
thanks,
greg k-h
drivers/i2c/chips/it87.c | 2 +-
drivers/i2c/chips/via686a.c | 7 ++-----
drivers/w1/w1.c | 9 +++++----
drivers/w1/w1_smem.c | 4 ++--
4 files changed, 10 insertions(+), 12 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>,
linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Date: Mon, 18 Apr 2005 21:39:38 -0700 [thread overview]
Message-ID: <20050419043938.GA23724@kroah.com> (raw)
Alright, let's try some small i2c and w1 patches...
Could you merge with:
kernel.org/pub/scm/linux/kernel/git/gregkh/i2c-2.6.git/
It contains 4 small patches, 2 i2c and 2 w1 bugfixes, diffstat is
below, I'll figure out how to send the individual patches later.
thanks,
greg k-h
drivers/i2c/chips/it87.c | 2 +-
drivers/i2c/chips/via686a.c | 7 ++-----
drivers/w1/w1.c | 9 +++++----
drivers/w1/w1_smem.c | 4 ++--
4 files changed, 10 insertions(+), 12 deletions(-)
next reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 4:39 Greg KH [this message]
2005-05-19 6:25 ` [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2 Greg KH
2005-04-19 18:58 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-04-19 19:40 ` Linus Torvalds
2005-05-19 6:25 ` Linus Torvalds
2005-04-19 19:47 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-04-19 20:20 ` Linus Torvalds
2005-05-19 6:25 ` Linus Torvalds
2005-04-19 21:40 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-04-19 22:00 ` Linus Torvalds
2005-04-19 22:27 ` Daniel Jacobowitz
2005-04-19 22:33 ` Greg KH
2005-04-19 23:04 ` Kenneth Johansson
2005-04-19 22:47 ` Linus Torvalds
2005-04-19 22:29 ` Martin Schlemmer
2005-04-19 22:43 ` Linus Torvalds
2005-04-19 23:11 ` Martin Schlemmer
2005-04-20 0:01 ` Jan-Benedict Glaw
2005-04-19 22:52 ` Lars Fenneberg
2005-04-19 22:39 ` Petr Baudis
2005-05-19 6:25 ` Petr Baudis
2005-04-19 22:49 ` Linus Torvalds
2005-05-19 6:25 ` Linus Torvalds
2005-04-19 22:19 ` Steven Cole
2005-05-19 6:25 ` Steven Cole
2005-04-19 22:26 ` Petr Baudis
2005-05-19 6:25 ` Petr Baudis
2005-04-19 22:45 ` Junio C Hamano
2005-05-19 6:25 ` Junio C Hamano
2005-04-19 22:58 ` Petr Baudis
2005-05-19 6:25 ` Petr Baudis
2005-04-19 22:38 ` Linus Torvalds
2005-05-19 6:25 ` Linus Torvalds
2005-04-19 23:02 ` Petr Baudis
2005-05-19 6:25 ` Petr Baudis
2005-04-19 23:04 ` Steven Cole
2005-05-19 6:25 ` Steven Cole
2005-04-19 23:16 ` Petr Baudis
2005-05-19 6:25 ` Petr Baudis
2005-04-19 23:38 ` Linus Torvalds
2005-05-19 6:25 ` Linus Torvalds
2005-04-19 23:41 ` Steven Cole
2005-05-19 6:25 ` Steven Cole
2005-04-20 16:56 ` Zlatko Calusic
2005-04-20 17:15 ` Linus Torvalds
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=20050419043938.GA23724@kroah.com \
--to=gregkh@suse.de \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
--cc=torvalds@osdl.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.