On Wed, Mar 21, 2018 at 08:32:54PM -0400, Jerome Glisse wrote:
> > I am testing with drivers/char/hmm_dmirror.c from your git repository.
> >
> > The addr I got (before "- size") is actually 0x7f, so equally
> > (1 << 40).
> >
> > So from your reply, it seems to me that HMM is supposed
On Wed, Mar 21, 2018 at 08:32:54PM -0400, Jerome Glisse wrote:
> > I am testing with drivers/char/hmm_dmirror.c from your git repository.
> >
> > The addr I got (before "- size") is actually 0x7f, so equally
> > (1 << 40).
> >
> > So from your reply, it seems to me that HMM is supposed
On Wed, Mar 21, 2018 at 05:23:55PM -0700, Nicolin Chen wrote:
> On Wed, Mar 21, 2018 at 06:56:32PM -0400, Jerome Glisse wrote:
> > On Wed, Mar 21, 2018 at 03:23:57PM -0700, Nicolin Chen wrote:
> > > Hello Jerome,
> > >
> > > I started to looking at the mm/hmm code and having a question at the
> >
On Wed, Mar 21, 2018 at 05:23:55PM -0700, Nicolin Chen wrote:
> On Wed, Mar 21, 2018 at 06:56:32PM -0400, Jerome Glisse wrote:
> > On Wed, Mar 21, 2018 at 03:23:57PM -0700, Nicolin Chen wrote:
> > > Hello Jerome,
> > >
> > > I started to looking at the mm/hmm code and having a question at the
> >
On Wed, Mar 21, 2018 at 06:56:32PM -0400, Jerome Glisse wrote:
> On Wed, Mar 21, 2018 at 03:23:57PM -0700, Nicolin Chen wrote:
> > Hello Jerome,
> >
> > I started to looking at the mm/hmm code and having a question at the
> > devm_request_mem_region() call in the hmm_devmem_add() implementation:
On Wed, Mar 21, 2018 at 06:56:32PM -0400, Jerome Glisse wrote:
> On Wed, Mar 21, 2018 at 03:23:57PM -0700, Nicolin Chen wrote:
> > Hello Jerome,
> >
> > I started to looking at the mm/hmm code and having a question at the
> > devm_request_mem_region() call in the hmm_devmem_add() implementation:
On Wed, Mar 21, 2018 at 03:23:57PM -0700, Nicolin Chen wrote:
> Hello Jerome,
>
> I started to looking at the mm/hmm code and having a question at the
> devm_request_mem_region() call in the hmm_devmem_add() implementation:
>
> > addr = min((unsigned long)iomem_resource.end,
> >
On Wed, Mar 21, 2018 at 03:23:57PM -0700, Nicolin Chen wrote:
> Hello Jerome,
>
> I started to looking at the mm/hmm code and having a question at the
> devm_request_mem_region() call in the hmm_devmem_add() implementation:
>
> > addr = min((unsigned long)iomem_resource.end,
> >
Hello Jerome,
I started to looking at the mm/hmm code and having a question at the
devm_request_mem_region() call in the hmm_devmem_add() implementation:
> addr = min((unsigned long)iomem_resource.end,
> (1UL << MAX_PHYSMEM_BITS) - 1);
The main question is here as I am a
Hello Jerome,
I started to looking at the mm/hmm code and having a question at the
devm_request_mem_region() call in the hmm_devmem_add() implementation:
> addr = min((unsigned long)iomem_resource.end,
> (1UL << MAX_PHYSMEM_BITS) - 1);
The main question is here as I am a
Sorry for simple question.
2. What is useful use of pagemap for troubleshooting?
I like to know PFN mapping, but my boss says
"On RHEL6 and RHEL7, what can we use for?"
For example, we can use the USS(Unique Set Size) to invest process memory leak.
Calculating USS
/proc/PID/p
Sorry for simple question.
1. Why physical address is greater than the installed memory?
-- Installed memory is 8GB
RHEL7# grep MemTotal /proc/meminfo
MemTotal:7840900 kB
RHEL7# dmidecode | grep -A 5 'Memory Device' | grep Size
Size: 4096 MB
Size: No Module Installed
Sorry for simple question.
2. What is useful use of pagemap for troubleshooting?
I like to know PFN mapping, but my boss says
On RHEL6 and RHEL7, what can we use for?
For example, we can use the USS(Unique Set Size) to invest process memory leak.
Calculating USS
/proc/PID/pagemap has
Sorry for simple question.
1. Why physical address is greater than the installed memory?
-- Installed memory is 8GB
RHEL7# grep MemTotal /proc/meminfo
MemTotal:7840900 kB
RHEL7# dmidecode | grep -A 5 'Memory Device' | grep Size
Size: 4096 MB
Size: No Module Installed
Thank you! I still have a long way to go in kernel.
2013/11/1 Andreas Mohr :
> Hi,
>
>> May I can use the ''double" as a basic variables?
>
> [see other replies]
>
>
> Look into terminus technicus "scaling math" as a replacement technique
> (in-kernel this is being used e.g. by
Hi,
> May I can use the ''double" as a basic variables?
[see other replies]
Look into terminus technicus "scaling math" as a replacement technique
(in-kernel this is being used e.g. by clocksources/clockevents).
HTH,
Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe
On 2013/10/31 19:31, 韩磊 wrote:
> May I can use the ''double" as a basic variables?
>
> When I define the "double" as a function return type in linux kernel,the error
> is "error: SSE register return with SSE disabled".
>
> How to fix it??
no float in kernel!
> --
> To unsubscribe from this
2013-10-31 12:57 keltezéssel, Richard Weinberger írta:
> On Thu, Oct 31, 2013 at 12:31 PM, 韩磊 wrote:
>> May I can use the ''double" as a basic variables?
>>
>> When I define the "double" as a function return type in linux kernel,the
>> error
>> is "error: SSE register return with SSE
On Thu, Oct 31, 2013 at 12:31 PM, 韩磊 wrote:
> May I can use the ''double" as a basic variables?
>
> When I define the "double" as a function return type in linux kernel,the error
> is "error: SSE register return with SSE disabled".
>
> How to fix it??
Don't do it. :)
In kernel land we don't
May I can use the ''double" as a basic variables?
When I define the "double" as a function return type in linux kernel,the error
is "error: SSE register return with SSE disabled".
How to fix it??
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
May I can use the ''double as a basic variables?
When I define the double as a function return type in linux kernel,the error
is error: SSE register return with SSE disabled.
How to fix it??
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Thu, Oct 31, 2013 at 12:31 PM, 韩磊 bonben1...@gmail.com wrote:
May I can use the ''double as a basic variables?
When I define the double as a function return type in linux kernel,the error
is error: SSE register return with SSE disabled.
How to fix it??
Don't do it. :)
In kernel land we
2013-10-31 12:57 keltezéssel, Richard Weinberger írta:
On Thu, Oct 31, 2013 at 12:31 PM, 韩磊 bonben1...@gmail.com wrote:
May I can use the ''double as a basic variables?
When I define the double as a function return type in linux kernel,the
error
is error: SSE register return with SSE
On 2013/10/31 19:31, 韩磊 wrote:
May I can use the ''double as a basic variables?
When I define the double as a function return type in linux kernel,the error
is error: SSE register return with SSE disabled.
How to fix it??
no float in kernel!
--
To unsubscribe from this list: send the
Hi,
May I can use the ''double as a basic variables?
[see other replies]
Look into terminus technicus scaling math as a replacement technique
(in-kernel this is being used e.g. by clocksources/clockevents).
HTH,
Andreas Mohr
--
To unsubscribe from this list: send the line unsubscribe
Thank you! I still have a long way to go in kernel.
2013/11/1 Andreas Mohr a...@lisas.de:
Hi,
May I can use the ''double as a basic variables?
[see other replies]
Look into terminus technicus scaling math as a replacement technique
(in-kernel this is being used e.g. by
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
> > panic_on_oops has no effect, a bunch of stuff flies past and the last
> > thing I see is "gam_server: scheduling while atomic" then a stack trace
> > of the core dump path then "Aiee, killing interrupt handler".
> >
> > I am starting to
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
> > panic_on_oops has no effect, a bunch of stuff flies past and the last
> > thing I see is "gam_server: scheduling while atomic" then a stack trace
> > of the core dump path then "Aiee, killing interrupt handler".
> >
> > I am starting to
> panic_on_oops has no effect, a bunch of stuff flies past and the last
> thing I see is "gam_server: scheduling while atomic" then a stack trace
> of the core dump path then "Aiee, killing interrupt handler".
>
> I am starting to suspect the hard drive, does that sound plausible?
> It's as if it
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
> On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
>
> > I have a machine here that oopses reliably when I start X, but the
> > interesting stuff scrolls away too fast, and a bunch more Oopses get
> > printed ending with "Aieee,
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
> On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
>
> > I have a machine here that oopses reliably when I start X, but the
> > interesting stuff scrolls away too fast, and a bunch more Oopses get
> > printed ending with "Aieee,
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
> I have a machine here that oopses reliably when I start X, but the
> interesting stuff scrolls away too fast, and a bunch more Oopses get
> printed ending with "Aieee, killing interrupt handler".
>
> How do I get the output to stop
On Sat, 2005-07-30 at 19:48 -0400, Lee Revell wrote:
> I have a machine here that oopses reliably when I start X, but the
> interesting stuff scrolls away too fast, and a bunch more Oopses get
> printed ending with "Aieee, killing interrupt handler".
>
> How do I get the output to stop after the
On Sat, 2005-07-30 at 19:48 -0400, Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing interrupt handler.
How do I get the output to stop after the first
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing interrupt handler.
How do I get the output to stop after the
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard drive, does that sound plausible?
It's as if it locks up
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard
--- Vojtech Pavlik <[EMAIL PROTECTED]> a écrit :
> >
> > I can't find "pinpad/input0" in sysfs, does that mean I need to add sysfs
> > suppport in my driver, and it's not done in input module when I register
> > my input driver ?
>
> I'm sorry, I thought it's already in mainline, but that bit
On Tue, Jul 26, 2005 at 02:26:02PM +0200, moreau francis wrote:
> Thanks Vojtech for your answers !
>
> --- Vojtech Pavlik <[EMAIL PROTECTED]> a écrit :
>
> > It's also available via an ioctl() and in sysfs. This allows you to
> > specify in an application that you want a device plugged into a
Thanks Vojtech for your answers !
--- Vojtech Pavlik <[EMAIL PROTECTED]> a écrit :
> It's also available via an ioctl() and in sysfs. This allows you to
> specify in an application that you want a device plugged into a specific
> port of the machine. Not many applications can use it at the
On Tue, Jul 26, 2005 at 01:47:05PM +0200, moreau francis wrote:
> hello,
>
> --- Vojtech Pavlik <[EMAIL PROTECTED]> a écrit :
>
> > > What is this field for ?
> >
> > It is intended for identifying the device based on "location" in the
> > system.
> >
>
> hmm, sorry but I don't understand
hello,
--- Vojtech Pavlik <[EMAIL PROTECTED]> a écrit :
> > What is this field for ?
>
> It is intended for identifying the device based on "location" in the
> system.
>
hmm, sorry but I don't understand you. I initialised this field with
"pinpad/input0" but the only place I can grep or find
On Tue, Jul 26, 2005 at 12:23:40PM +0200, moreau francis wrote:
> I'm currently developping a very simple driver for a pinpad by using
> Input module. I'm using Event handler to pass events from pinpad to userland.
> In this simple case, I'm wondering if I really need to initialise
> "phys" field
Hi,
I'm currently developping a very simple driver for a pinpad by using
Input module. I'm using Event handler to pass events from pinpad to userland.
In this simple case, I'm wondering if I really need to initialise
"phys" field in in "input_dev" struct before calling "input_register_device".
Hi,
I'm currently developping a very simple driver for a pinpad by using
Input module. I'm using Event handler to pass events from pinpad to userland.
In this simple case, I'm wondering if I really need to initialise
phys field in in input_dev struct before calling input_register_device.
What is
On Tue, Jul 26, 2005 at 12:23:40PM +0200, moreau francis wrote:
I'm currently developping a very simple driver for a pinpad by using
Input module. I'm using Event handler to pass events from pinpad to userland.
In this simple case, I'm wondering if I really need to initialise
phys field in in
hello,
--- Vojtech Pavlik [EMAIL PROTECTED] a écrit :
What is this field for ?
It is intended for identifying the device based on location in the
system.
hmm, sorry but I don't understand you. I initialised this field with
pinpad/input0 but the only place I can grep or find it, is in
On Tue, Jul 26, 2005 at 01:47:05PM +0200, moreau francis wrote:
hello,
--- Vojtech Pavlik [EMAIL PROTECTED] a écrit :
What is this field for ?
It is intended for identifying the device based on location in the
system.
hmm, sorry but I don't understand you. I initialised this
Thanks Vojtech for your answers !
--- Vojtech Pavlik [EMAIL PROTECTED] a écrit :
It's also available via an ioctl() and in sysfs. This allows you to
specify in an application that you want a device plugged into a specific
port of the machine. Not many applications can use it at the moment,
On Tue, Jul 26, 2005 at 02:26:02PM +0200, moreau francis wrote:
Thanks Vojtech for your answers !
--- Vojtech Pavlik [EMAIL PROTECTED] a écrit :
It's also available via an ioctl() and in sysfs. This allows you to
specify in an application that you want a device plugged into a specific
--- Vojtech Pavlik [EMAIL PROTECTED] a écrit :
I can't find pinpad/input0 in sysfs, does that mean I need to add sysfs
suppport in my driver, and it's not done in input module when I register
my input driver ?
I'm sorry, I thought it's already in mainline, but that bit is still
On Sun, Jul 10, 2005 at 01:41:40PM +0800, guorke wrote:
> like:
>
> /*
> @@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
> do_page_fault(stru
>struct vm_area_struct * vma;
>unsigned long address;
>unsigned long page;
> - int write;
> -
On Sun, 10 Jul 2005 13:41:40 +0800 guorke wrote:
| like:
|
| /*
| @@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
| do_page_fault(stru
|struct vm_area_struct * vma;
|unsigned long address;
|unsigned long page;
| - int write;
| -
On Sun, 10 Jul 2005 13:41:40 +0800 guorke wrote:
| like:
|
| /*
| @@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
| do_page_fault(stru
|struct vm_area_struct * vma;
|unsigned long address;
|unsigned long page;
| - int write;
| -
On Sun, Jul 10, 2005 at 01:41:40PM +0800, guorke wrote:
like:
/*
@@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
do_page_fault(stru
struct vm_area_struct * vma;
unsigned long address;
unsigned long page;
- int write;
- siginfo_t
On 7/10/05, guorke <[EMAIL PROTECTED]> wrote:
> like:
>
> /*
> @@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
> do_page_fault(stru
> struct vm_area_struct * vma;
> unsigned long address;
> unsigned long page;
> - int write;
> - siginfo_t
like:
/*
@@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
do_page_fault(stru
struct vm_area_struct * vma;
unsigned long address;
unsigned long page;
- int write;
- siginfo_t info;
-
+ int write, si_code;
+
/* get the address */
like:
/*
@@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
do_page_fault(stru
struct vm_area_struct * vma;
unsigned long address;
unsigned long page;
- int write;
- siginfo_t info;
-
+ int write, si_code;
+
/* get the address */
On 7/10/05, guorke [EMAIL PROTECTED] wrote:
like:
/*
@@ -220,9 +232,8(HERE: why not -220,9 +220,8) @@ fastcall notrace void
do_page_fault(stru
struct vm_area_struct * vma;
unsigned long address;
unsigned long page;
- int write;
- siginfo_t info;
-
+
Ahh, very nice, thanks!
On Sat, 5 Feb 2005, Randy.Dunlap wrote:
Justin Piszcz wrote:
Why are there only 7-8 loop devices available?
What options do I have if I want to mount, say, 100 isos?
Documentation/kernel-parameters.txt say:
max_loop= [LOOP] Maximum number of loopback devices that can
Justin Piszcz wrote:
Why are there only 7-8 loop devices available?
What options do I have if I want to mount, say, 100 isos?
Documentation/kernel-parameters.txt say:
max_loop= [LOOP] Maximum number of loopback devices that can
be mounted
Format: <1-256>
--
Justin Piszcz wrote:
Why are there only 7-8 loop devices available?
What options do I have if I want to mount, say, 100 isos?
Documentation/kernel-parameters.txt say:
max_loop= [LOOP] Maximum number of loopback devices that can
be mounted
Format: 1-256
--
Ahh, very nice, thanks!
On Sat, 5 Feb 2005, Randy.Dunlap wrote:
Justin Piszcz wrote:
Why are there only 7-8 loop devices available?
What options do I have if I want to mount, say, 100 isos?
Documentation/kernel-parameters.txt say:
max_loop= [LOOP] Maximum number of loopback devices that can
If you do a make install, it will be copied to /boot directory
automatically;-)
Alex
On Mon, 7 May 2001, Hai Xu wrote:
> Dear all,
>
> After I compile and upgrade to a newer Kernel, do I need to copy the
> System.map from /usr/src/linux/ to /boot/System- and link it to
> System.map?
>
>
On 07 May 2001 11:29:56 -0400, Hai Xu wrote:
> After I compile and upgrade to a newer Kernel, do I need to copy the
> System.map from /usr/src/linux/ to /boot/System- and link it to
> System.map
yes, you do. but System.map is only needed to do symbol lookups, for
times like debugging.
note
Dear all,
After I compile and upgrade to a newer Kernel, do I need to copy the
System.map from /usr/src/linux/ to /boot/System- and link it to
System.map?
Thanks in advance
Hai Xu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Dear all,
After I compile and upgrade to a newer Kernel, do I need to copy the
System.map from /usr/src/linux/ to /boot/System- and link it to
System.map?
Thanks in advance
Hai Xu
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On 07 May 2001 11:29:56 -0400, Hai Xu wrote:
After I compile and upgrade to a newer Kernel, do I need to copy the
System.map from /usr/src/linux/ to /boot/System- and link it to
System.map
yes, you do. but System.map is only needed to do symbol lookups, for
times like debugging.
note
If you do a make install, it will be copied to /boot directory
automatically;-)
Alex
On Mon, 7 May 2001, Hai Xu wrote:
Dear all,
After I compile and upgrade to a newer Kernel, do I need to copy the
System.map from /usr/src/linux/ to /boot/System- and link it to
System.map?
Thanks
Hi,
Just wonder what exactly the difference between buffer and cache in linux
memory management is.
Cache is used for filesystems, so that files read from a fs are kept in
memory in order to provide faster access next time.
Then what is buffer used for?
As executables are also kept in memory,
Hi,
Just wonder what exactly the difference between buffer and cache in linux
memory management is.
Cache is used for filesystems, so that files read from a fs are kept in
memory in order to provide faster access next time.
Then what is buffer used for?
As executables are also kept in memory,
Hello!
> I've scrolled through various code in net/ipv4, and I can't see how to query
> the TOS of an incoming TCP stream (or at the least, the TOS of the SYN which
> initiated the connection).
No way. Formally it is IP_RECVTOS, followed by IP_PKTOPTIONS.
But getting TOS via IP_PKTOPTIONS is
Hello!
I've scrolled through various code in net/ipv4, and I can't see how to query
the TOS of an incoming TCP stream (or at the least, the TOS of the SYN which
initiated the connection).
No way. Formally it is IP_RECVTOS, followed by IP_PKTOPTIONS.
But getting TOS via IP_PKTOPTIONS is not
> getsockopt(fd, SOL_IP, IP_TOS, ..
Doesn't work. Returns the TOS of outgoing packets, which defaults to 0 even if
there is a TOS set on incoming traffic... that was what I tried in my first
test program.
David.
> cheers,
>
> lincoln.
>
> At 03:00 PM 7/03/2001 +1100, David Luyer wrote:
>
getsockopt(fd, SOL_IP, IP_TOS, ..
cheers,
lincoln.
At 03:00 PM 7/03/2001 +1100, David Luyer wrote:
>I've scrolled through various code in net/ipv4, and I can't see how to query
>the TOS of an incoming TCP stream (or at the least, the TOS of the SYN which
>initiated the connection).
>
I've scrolled through various code in net/ipv4, and I can't see how to query
the TOS of an incoming TCP stream (or at the least, the TOS of the SYN which
initiated the connection).
Someone has sent in a feature request for squid which would require this,
presumably so they can set the TOS in
I've scrolled through various code in net/ipv4, and I can't see how to query
the TOS of an incoming TCP stream (or at the least, the TOS of the SYN which
initiated the connection).
Someone has sent in a feature request for squid which would require this,
presumably so they can set the TOS in
getsockopt(fd, SOL_IP, IP_TOS, ..
Doesn't work. Returns the TOS of outgoing packets, which defaults to 0 even if
there is a TOS set on incoming traffic... that was what I tried in my first
test program.
David.
cheers,
lincoln.
At 03:00 PM 7/03/2001 +1100, David Luyer wrote:
I've
On Sat, Mar 03, 2001 at 02:14:18PM -0500, Albert D. Cahalan wrote:
> David G\363mez writes:
>
> > Hi, i've got a newbie question about patches:
> > Are the pre* patches ( and i guess also the ac* ones) applied against the
> > last release of the kernel or against the previous patch? I mean, when
[cc trimmed]
On Sat, 3 Mar 2001, Alan Cox wrote:
> > Long ago, pre* and ac* patches were rare. Patches went from one
>
> Umm wrong. -ac patches for 2.2 regularly did one a day
>
> > line-by-line before the next one came out. Patches always applied
> > easily with the (pre-POSIX?) patch
> Long ago, pre* and ac* patches were rare. Patches went from one
Umm wrong. -ac patches for 2.2 regularly did one a day
> line-by-line before the next one came out. Patches always applied
> easily with the (pre-POSIX?) patch command. Version numbers made
patch is Larry Wall
> Pre-patches go
David G\363mez writes:
> Hi, i've got a newbie question about patches:
> Are the pre* patches ( and i guess also the ac* ones) applied against the
> last release of the kernel or against the previous patch? I mean, when
> 2.4.3pre2 will come out, i need to get also the pre1 patch?
Really, I
On Saturday 03 March 2001 12:18 pm, [EMAIL PROTECTED] wrote:
> Hi, i've got a newbie question about patches:
> Are the pre* patches ( and i guess also the ac* ones) applied against the
> last release of the kernel or against the previous patch? I mean, when
> 2.4.3pre2 will come out, i need to
On Saturday 03 March 2001 12:18 pm, [EMAIL PROTECTED] wrote:
Hi, i've got a newbie question about patches:
Are the pre* patches ( and i guess also the ac* ones) applied against the
last release of the kernel or against the previous patch? I mean, when
2.4.3pre2 will come out, i need to get
David G\363mez writes:
Hi, i've got a newbie question about patches:
Are the pre* patches ( and i guess also the ac* ones) applied against the
last release of the kernel or against the previous patch? I mean, when
2.4.3pre2 will come out, i need to get also the pre1 patch?
Really, I
[cc trimmed]
On Sat, 3 Mar 2001, Alan Cox wrote:
Long ago, pre* and ac* patches were rare. Patches went from one
Umm wrong. -ac patches for 2.2 regularly did one a day
line-by-line before the next one came out. Patches always applied
easily with the (pre-POSIX?) patch command.
On Sat, Mar 03, 2001 at 02:14:18PM -0500, Albert D. Cahalan wrote:
David G\363mez writes:
Hi, i've got a newbie question about patches:
Are the pre* patches ( and i guess also the ac* ones) applied against the
last release of the kernel or against the previous patch? I mean, when
90 matches
Mail list logo
