Please everyone stop Cc:ing me on this discussion, I have no interest
and nothing to contribute here.
I have set an invalid Reply-To: just in case...
Am 07.10.19 um 11:32 schrieb Mika Westerberg:
> On Sat, Oct 05, 2019 at 09:34:41AM +0200, Matthias Andree wrote:
>> Am 04.10.19 um 15:06 schrieb Mika Westerberg:
>>> On Fri, Oct 04, 2019 at 02:57:21PM +0200, Matthias Andree wrote:
>>>> Am 04.10.19 um 14:39 schrieb Mi
Am 04.10.19 um 15:06 schrieb Mika Westerberg:
> On Fri, Oct 04, 2019 at 02:57:21PM +0200, Matthias Andree wrote:
>> Am 04.10.19 um 14:39 schrieb Mika Westerberg:
>>> @Matthias, @Paul and @Nicholas, I appreciate if you could check that this
>>> does not cause any issue
Am 04.10.19 um 14:39 schrieb Mika Westerberg:
> @Matthias, @Paul and @Nicholas, I appreciate if you could check that this
> does not cause any issues for your systems.
Just to be sure: is this intended to be applied against the 5.4-rc*
master branch?
Am 26.08.19 um 16:42 schrieb Mika Westerberg:
> According to PCI FW 3.2 the OS is responsible for those delays if the
> platform firmware does not provide that _DSM. So simpler way would be
> always do the delays if the _DSM is not there.
Well, that is
* unless we trip over delays that make
Am 21.08.19 um 14:45 schrieb Mika Westerberg:
> Hi all,
>
> As the changelog says this is reworked version that tries to avoid reported
> issues while at the same time fix the missing delays so we can get ICL
> systems and at least the one system with Titan Ridge controller working
> properly.
>
>
[please remember to Cc: me on your replies]
Greetings,
is there an easy way to dump a process's pagetables from outside that
process? Tools, /proc or /sys file or syscall that I missed?
Thanks in advance.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe
[please remember to Cc: me on your replies]
Greetings,
is there an easy way to dump a process's pagetables from outside that
process? Tools, /proc or /sys file or syscall that I missed?
Thanks in advance.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux
ng out duplicate code - or they decided
that would be a more boring job than porting ZFS :-)
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordom
ke it
difficult to verify assumptions/expectations or assess potential
solutions (such as the res_init() issue in fetchmail, or probably the khubd
going
south issue in Linux), but that's not the point.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
s going to be tough to obtain all the preciou
bug from bugzzzilla but anyways, if nobody likes
to use it, something will be done and if only neglect...)
HTH
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
bug from bugzzzilla but anyways, if nobody likes
to use it, something will be done and if only neglect...)
HTH
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
assumptions/expectations or assess potential
solutions (such as the res_init() issue in fetchmail, or probably the khubd
going
south issue in Linux), but that's not the point.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
- or they decided
that would be a more boring job than porting ZFS :-)
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
that's going to leave you with tons of dirty buffers that clear slowly
-- "watch -n 1 grep -i dirty /proc/meminfo" is boring, but elucidating...
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROT
ad write to new
> blocks with version numbers (and not re-use old blocks until new versions
> are stable on disk).
Only that you need direct-overwrite support to be able to safely trash
data you no longer need...
--
Matthias Andree
-
To unsubscribe from this list: send the line &quo
or some other big write, if somebody fsync'ed a small
> file, it wasn't even a blip on the radar - the fsync would sync just that
> small thing.
It's not as though I'd recommend reiserfs. I have seen one major
corruption recently in openSUSE 10.2 with ext3, but I've had constant
headaches w
corruption recently in openSUSE 10.2 with ext3, but I've had constant
headaches with reiserfs since the day it went into S.u.S.E. kernels at
the time until I switched away from reiserfs some years ago.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
blocks with version numbers (and not re-use old blocks until new versions
are stable on disk).
Only that you need direct-overwrite support to be able to safely trash
data you no longer need...
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
going to leave you with tons of dirty buffers that clear slowly
-- watch -n 1 grep -i dirty /proc/meminfo is boring, but elucidating...
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Sat, 14 Apr 2007, Alan Stern wrote:
> On Sat, 14 Apr 2007, Matthias Andree wrote:
>
> > I arrived at the computer today, to find khubd in D state again, but
> > unfortunately, it does not show up in Alt-SysRq-T output. Do kernel
> > threads show up there at all? 2.6.18
On Sat, 14 Apr 2007, Alan Stern wrote:
On Sat, 14 Apr 2007, Matthias Andree wrote:
I arrived at the computer today, to find khubd in D state again, but
unfortunately, it does not show up in Alt-SysRq-T output. Do kernel
threads show up there at all? 2.6.18.8-0.1 with SUSE patches
On Mon, 09 Apr 2007, Alan Stern wrote:
> On Mon, 9 Apr 2007, Matthias Andree wrote:
>
> > Please Cc: me on replies, as I read linux-kernel sporadically and am not
> > subscribed to linux-usb-devel at all.
> >
> > Greetings,
> >
> > I have seen my USB
. Any specific kernel debugging
options that might help me debug this further?
Thanks,
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.h
. Any specific kernel debugging
options that might help me debug this further?
Thanks,
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
wer - which
kernel version are you using? If it's a Fedora-patched kernel, report
the problem to the Fedora project. If it's an older unmodified kernel,
retry with a newer kernel (2.6.12.3) first and see if the problem is
still present.
--
Matthias Andree
-
To unsubscribe from this list: send the
are you using? If it's a Fedora-patched kernel, report
the problem to the Fedora project. If it's an older unmodified kernel,
retry with a newer kernel (2.6.12.3) first and see if the problem is
still present.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux
c: At top level:
sound/pci/bt87x.c:910: error: `driver' used prior to declaration
make[2]: *** [sound/pci/bt87x.o] Error 1
make[1]: *** [sound/pci] Error 2
make: *** [sound] Error 2
configuration attached.
--
Matthias Andree
config.gz
Description: application/gunzip
sed prior to declaration
make[2]: *** [sound/pci/bt87x.o] Error 1
make[1]: *** [sound/pci] Error 2
make: *** [sound] Error 2
configuration attached.
--
Matthias Andree
config.gz
Description: application/gunzip
to declaration
make[2]: *** [sound/pci/bt87x.o] Error 1
make[1]: *** [sound/pci] Error 2
make: *** [sound] Error 2
configuration attached.
--
Matthias Andree
config.gz
Description: application/gunzip
level:
sound/pci/bt87x.c:910: error: `driver' used prior to declaration
make[2]: *** [sound/pci/bt87x.o] Error 1
make[1]: *** [sound/pci] Error 2
make: *** [sound] Error 2
configuration attached.
--
Matthias Andree
config.gz
Description: application/gunzip
ng-Lists/securityfocus/bugtraq/2004-12/0106.html>
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
lk > $mk) { $mk = $lk; }
if ($lv > $mv) { $mv = $lv; }
}
print "max key len $mk, max val len $mv\n";
----
which prints: (key is the email, val the name)
max key len 43, max val len 36
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe lin
is the email, val the name)
max key len 43, max val len 36
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
the hacking POV as the code is available and under an
acceptable license.
Getting DARCS up to the task would probably require some polishing, and
should probably be discussed with the DARCS maintainer before making
this decision.
Don't get me wrong, DARCS looks promising, but I'm not convince
polishing, and
should probably be discussed with the DARCS maintainer before making
this decision.
Don't get me wrong, DARCS looks promising, but I'm not convinced it's
ready for the linux kernel yet.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED],
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED],
You can use export or mount options to make
NFS asynchronous.
Plus, NFS3 has write clustering which may be worth a try depending on
your workload.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
to make
NFS asynchronous.
Plus, NFS3 has write clustering which may be worth a try depending on
your workload.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
Boomerang cards.)
I'll try 2.6.11 as workload permits, the machine is a router in
production with SuSE 9.2 (2.6.8 + SuSE hacks, "2.6.8-24.11-default")
kernel.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
as workload permits, the machine is a router in
production with SuSE 9.2 (2.6.8 + SuSE hacks, 2.6.8-24.11-default)
kernel.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
ny insight into these would be appreciated,
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
into these would be appreciated,
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED],
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED],
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED],
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED],
On Sat, 12 Mar 2005, Greg KH wrote:
> A bitkeeper tree for the 2.6.11.y releases can be found at:
> bk://linux-release.bkbits.net/linux-2.6.11
Do we then start switching trees with every new minor release?
--
Matthias Andree
-
To unsubscribe from this list: send the line "
On Sat, 12 Mar 2005, Greg KH wrote:
A bitkeeper tree for the 2.6.11.y releases can be found at:
bk://linux-release.bkbits.net/linux-2.6.11
Do we then start switching trees with every new minor release?
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux
' => 'Liam Girdwood',
'liam.girdwood:wolfsonmicro.com' => 'Liam Girdwood',
'libor:topspin.com' => 'Libor Michalek',
+'liml:rtr.ca' => 'Mark Lord',
'linas:austin.ibm.com' => 'Linas Vepstas',
'linas:linas.org' => 'Linas Vepstas',
'linas:us.ibm.com' => 'Linas Vepstas',
@@ -17
',
'matthias.andree:gmx.de' = 'Matthias Andree', # added by himself
'matthias.christian:tiscali.de' = 'Matthias-Christian Ott',
+'matthias.kunze:gmx-topmail.de' = 'Matthias Kunze',
'matthias:net.rmk.(none)' = 'Matthias Burghardt',
'mauelshagen:redhat.com' = 'Heinz J. Mauelshagen
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
is line, then upgrade your mailer or pipe this mail
= <- into metamail.
--
A sh script on behalf of Matthias Andree
-
Changes since last release:
revision 0.328
date: 2005-03-04 02:36:50 +; auth
changelog
script, using bk changes rather than bk prs, without affection output at
all. I have made such a change and committed it to my BK copy, see the
"shortlog" announcement I posted two minutes ago.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe l
Hello Linus,
this patch speeds up your "stupid release" script; in fact the hog was
in changelog itself the use of bk prs; this is known to be slow, and I'd
asked Larry if bk changes (which is A LOT faster) would have the same
effect months ago, and he approved using bk changes after bk set -d.
Hello Linus,
this patch speeds up your stupid release script; in fact the hog was
in changelog itself the use of bk prs; this is known to be slow, and I'd
asked Larry if bk changes (which is A LOT faster) would have the same
effect months ago, and he approved using bk changes after bk set -d.
So
script, using bk changes rather than bk prs, without affection output at
all. I have made such a change and committed it to my BK copy, see the
shortlog announcement I posted two minutes ago.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
or pipe this mail
= - into metamail.
--
A sh script on behalf of Matthias Andree
-
Changes since last release:
revision 0.328
date: 2005-03-04 02:36:50 +; author: emma; state: Exp; lines: +200
On Wed, 02 Mar 2005, Linus Torvalds wrote:
> On Wed, 2 Mar 2005, Matthias Andree wrote:
> >
> > ftp.kernel.org:/pub/linux/kernel/v2.6 doesn't seem to carry a crypto
> > signature for the patch, patch-2.6.11.gz.sign
>
> It's there now (along with the Ch
On Wed, 02 Mar 2005, Linus Torvalds wrote:
> there it is. Only small stuff lately - as promised. Shortlog from -rc5
> appended, nothing exciting there, mostly some fixes from various code
> checkers (like fixed init sections, and some coverity tool finds).
On Wed, 02 Mar 2005, Linus Torvalds wrote:
there it is. Only small stuff lately - as promised. Shortlog from -rc5
appended, nothing exciting there, mostly some fixes from various code
checkers (like fixed init sections, and some coverity tool finds).
ftp.kernel.org:/pub/linux/kernel/v2.6
On Wed, 02 Mar 2005, Linus Torvalds wrote:
On Wed, 2 Mar 2005, Matthias Andree wrote:
ftp.kernel.org:/pub/linux/kernel/v2.6 doesn't seem to carry a crypto
signature for the patch, patch-2.6.11.gz.sign
It's there now (along with the ChangeLog).
The signatures are automatically
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is file://var/bitkeeper/BK-kernel-tools
Patch description:
[EMAIL
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is file://var/bitkeeper/BK-kernel-tools
Patch description:
[EMAIL
hat. I've always wondered why Linux went backwards when all
other systems added atapicam (FreeBSD) and similar, now I can stop
wondering.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
always wondered why Linux went backwards when all
other systems added atapicam (FreeBSD) and similar, now I can stop
wondering.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
rice list on the web for individual users might
be very helpful though. It won't be used very often but simplify the
decision process a bit.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
ked to veil his intentions or out of
honest interest in consultations can only be judged after we've seen the
3.2.4 BK/Free license.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mor
e a year long gap and they have been happy with that answer
> but they are asking for us to put it in the license so they don't have
> to depend on some email based side agreement.
So have them send a SSAE and pass that note in writing.
--
Matthias Andree
-
To unsubscribe from this list: send
but they are asking for us to put it in the license so they don't have
to depend on some email based side agreement.
So have them send a SSAE and pass that note in writing.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
intentions or out of
honest interest in consultations can only be judged after we've seen the
3.2.4 BK/Free license.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
on the web for individual users might
be very helpful though. It won't be used very often but simplify the
decision process a bit.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
McClelland',
'mark:mtfhpc.demon.co.uk' => 'Mark Fortescue',
'mark:net.rmk.(none)' => 'Mark Hindley',
+'mark_salyzyn:adaptec.com' => 'Mark Salyzyn',
'markb:wetlettuce.com' => 'Mark Broadbent',
'markgw:sgi.com' => 'Mark Goodwin',
'markh:osdl.org' => 'Mark Haverkamp',
@@ -168
',
'markgw:sgi.com' = 'Mark Goodwin',
'markh:osdl.org' = 'Mark Haverkamp',
@@ -1683,6 +1701,7 @@
'matthewc:cse.unsw.edu.au' = 'Matthew Chapman',
'matthewn:snapgear.com' = 'Matthew Natalier',
'matthias.andree:gmx.de' = 'Matthias Andree', # added by himself
+'matthias.christian:tiscali.de
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Adrian Bunk schrieb am 2005-01-20:
> On Thu, Jan 20, 2005 at 10:27:58AM +0100, Matthias Andree wrote:
> >...
> > @@ -481,6 +482,7 @@
> >...
> > 'bunk:fs.tum.de' => 'Adrian Bunk',
> > 'bunk:stusta.de' => 'Adrian Bunk',
> > +'bunk:stutsa.de' =&g
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Hello Linus,
you can either use bk receive to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK: Parent repository is http://bktools.bkbits.net/bktools
Patch description:
[EMAIL
Adrian Bunk schrieb am 2005-01-20:
On Thu, Jan 20, 2005 at 10:27:58AM +0100, Matthias Andree wrote:
...
@@ -481,6 +482,7 @@
...
'bunk:fs.tum.de' = 'Adrian Bunk',
'bunk:stusta.de' = 'Adrian Bunk',
+'bunk:stutsa.de' = 'Adrian Bunk',
...
Where did you find this?
This is a typo
the "good" way not enough.
A complex system without proper documentation is worth _nothing_.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.
way not enough.
A complex system without proper documentation is worth _nothing_.
--
Matthias Andree
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
On Wed, 27 Jun 2001, Silviu Marin-Caea wrote:
> No matter what stupid things I do on it, I shouldn't be able to take the
> kernel down, right?
>
> After I replaced the Realtek with a 3com, I could see all of the 60
> instances fighting like worms in shit, but the server survived.
Did the card
On Wed, 27 Jun 2001, Silviu Marin-Caea wrote:
No matter what stupid things I do on it, I shouldn't be able to take the
kernel down, right?
After I replaced the Realtek with a 3com, I could see all of the 60
instances fighting like worms in shit, but the server survived.
Did the card share
On Sun, 24 Jun 2001, Rick Hohensee wrote:
> 2.4.5 is 26 meg now. It's time to consider forking the kernel. Alan has
> already stuck his tippy-toe is that pool, and his toe is fine.
> For a client-use Linux kernel, I suggest, and will be and have been
> persuing, features and non-features such
On Mon, 25 Jun 2001, Alexander V. Bilichenko wrote:
> Hello All!
> Some tests that I have recently check out.
> kernel compiled with 3.0 (2.4.5) function call: 100 iteration. 3% slower
> than 2.95.
> test example - hash table add/remove - 4% slower (compiled both
> with -O2 -march=i686).
>
On Mon, 25 Jun 2001, Alexander V. Bilichenko wrote:
Hello All!
Some tests that I have recently check out.
kernel compiled with 3.0 (2.4.5) function call: 100 iteration. 3% slower
than 2.95.
test example - hash table add/remove - 4% slower (compiled both
with -O2 -march=i686).
Why have
On Sun, 24 Jun 2001, Rick Hohensee wrote:
2.4.5 is 26 meg now. It's time to consider forking the kernel. Alan has
already stuck his tippy-toe is that pool, and his toe is fine.
For a client-use Linux kernel, I suggest, and will be and have been
persuing, features and non-features such
On Fri, 01 Jun 2001, Matthias Andree wrote:
> Not sure if it's related to IRQ sharing or another initialization issue.
Looks like IRQ sharing is still in the play.
Yesterday, I purchased a pair of used 3C905TXs, replaced the RTL 8139 by
the 3C905, and got complaints by the 3C905 about &q
On Fri, 01 Jun 2001, Matthias Andree wrote:
Not sure if it's related to IRQ sharing or another initialization issue.
Looks like IRQ sharing is still in the play.
Yesterday, I purchased a pair of used 3C905TXs, replaced the RTL 8139 by
the 3C905, and got complaints by the 3C905 about eth0
On Fri, 01 Jun 2001, Jeff Garzik wrote:
> Matthias Andree wrote:
> >
> > Will that 8139too be able to share its IRQ with a bttv card (Hauppauge
> > WinTV in my case)? With 2.2.19, it's currently possible, at least after
> > unloading and reloading the 8139too module,
On Fri, 01 Jun 2001, Jeff Garzik wrote:
Matthias Andree wrote:
Will that 8139too be able to share its IRQ with a bttv card (Hauppauge
WinTV in my case)? With 2.2.19, it's currently possible, at least after
unloading and reloading the 8139too module, but it's a no-go with 2.4.5.
Can
On Wed, 30 May 2001, Jeff Garzik wrote:
> > I see that Alan has reverted back to the 2.4.3 driver for his ac-series for
> > other reasons, hopefully either the old driver will going in to 2.4.6 or the
> > new one will get fixed?
>
> I've got one of the two problems fixed here at the test lab,
1 - 100 of 321 matches
Mail list logo