public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Miloslav Trmac <mitr@volny.cz>
Subject: Re: [git pull 00/14] Input updates for 2.6.15
Date: Mon, 21 Nov 2005 22:40:42 -0500	[thread overview]
Message-ID: <200511212240.42532.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0511201016220.13959@g5.osdl.org>

On Sunday 20 November 2005 13:17, Linus Torvalds wrote:
> 
> On Sun, 20 Nov 2005, Dmitry Torokhov wrote:
> > 
> > That cinergyT2 fix (from Linux-2.6.15-rc2 thread) - do you already have it
> > or would you prefer a pull prepared later tonight?
> 
> The only one I have is the one I got through davem a couple of days ago: 
> 
>   cinergyT2: cinergyt2_register_rc() should return 0 on success
> 
> is that the one you're talking about?
> 

Sorry for the delay...

I see that you already merged the patch I was talking about:

db93a82fa9d8b4d6e31c227922eaae829253bb88 [PATCH] Fix an OOPS is CinergyT2

-- 
Dmitry

      reply	other threads:[~2005-11-22  3:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  6:36 [git pull 00/14] Input updates for 2.6.15 Dmitry Torokhov
2005-11-20  6:36 ` [git pull 01/14] atkbd - speed up setting leds/repeat state Dmitry Torokhov
2005-11-20  6:36 ` [git pull 02/14] Add Wistron driver Dmitry Torokhov
2005-11-20  6:36 ` [git pull 03/14] Wistron - disable for x86_64 Dmitry Torokhov
2005-11-20  9:52   ` Geert Uytterhoeven
2005-11-22  3:42     ` Dmitry Torokhov
2005-11-20  6:36 ` [git pull 04/14] Wistron - add support for Acer Aspire notebooks Dmitry Torokhov
2005-11-20  6:36 ` [git pull 05/14] Wistron - convert to dynamic input_dev allocation Dmitry Torokhov
2005-11-20  6:36 ` [git pull 06/14] Wistron - add PM support Dmitry Torokhov
2005-11-20  6:36 ` [git pull 07/14] wistron - disable wifi/bluetooth on suspend Dmitry Torokhov
2005-11-20  6:36 ` [git pull 08/14] Uinput: convert to dynalloc allocation Dmitry Torokhov
2005-11-20  6:36 ` [git pull 09/14] Uinput: add UI_SET_SWBIT ioctl Dmitry Torokhov
2005-11-23 22:53   ` Benjamin Herrenschmidt
2005-11-23 23:06     ` Benjamin Herrenschmidt
2005-11-23 23:13       ` Dmitry Torokhov
2005-11-23 23:01   ` Benjamin Herrenschmidt
2005-11-23 23:12     ` Dmitry Torokhov
2005-11-23 23:28       ` Benjamin Herrenschmidt
2005-11-20  6:36 ` [git pull 10/14] Uinput: dont use "interruptible" in FF code Dmitry Torokhov
2005-11-20  6:36 ` [git pull 11/14] Handle failures in input_register_device() Dmitry Torokhov
2005-11-20  6:36 ` [git pull 12/14] Input - help swsusp Dmitry Torokhov
2005-11-20  6:36 ` [git pull 13/14] Input updates for 2.6.15 Dmitry Torokhov
2005-11-20  6:36 ` [git pull 14/14] Fix missing initialization in ir-kbd-gpio.c Dmitry Torokhov
2005-11-20  8:37 ` [git pull 00/14] Input updates for 2.6.15 Vojtech Pavlik
2005-11-20 17:04 ` Dmitry Torokhov
2005-11-20 17:19   ` Linus Torvalds
2005-11-20 17:42     ` Dmitry Torokhov
2005-11-20 18:17       ` Linus Torvalds
2005-11-22  3:40         ` Dmitry Torokhov [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=200511212240.42532.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitr@volny.cz \
    --cc=torvalds@osdl.org \
    --cc=vojtech@suse.cz \
    /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