From: Bart Samwel <bart@samwel.tk>
To: Kiko Piris <kernel@pirispons.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: A couple of questions about laptop-mode for 2.6, version 4
Date: Tue, 30 Dec 2003 13:31:57 +0100 [thread overview]
Message-ID: <3FF1703D.8050909@samwel.tk> (raw)
In-Reply-To: <20031230111408.GA22920@sacarino.pirispons.net>
Kiko Piris wrote:
> Btw, have you had reliability reports? Do you know if it's going to be
> included in 2.6 "official" tree shortly?
I've gotten no reliability reports whatsoever, but nobody's complained.
I've run it for a couple of days and it worked fine for me, so that give
me some level of confidence. As for your second question: I have no
clue, this is out of my hands. I'm not even sure if I have to do
anything specific (like officially submitting to Linus or something) in
order to have it included. Can anyone tell me how this is usually done?
Bart
prev parent reply other threads:[~2003-12-30 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031230092831.GA20414@sacarino.pirispons.net>
[not found] ` <3FF15849.60005@samwel.tk>
2003-12-30 11:14 ` Fwd: A couple of questions about laptop-mode for 2.6, version 4 Kiko Piris
2003-12-30 12:31 ` Bart Samwel [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=3FF1703D.8050909@samwel.tk \
--to=bart@samwel.tk \
--cc=kernel@pirispons.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox