Yes, I've tested the patch extensively. It's working fine for me.
Pavel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Yes, I've tested the patch extensively. It's working fine for me.
Pavel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
e should be no behavior change in get_prompt_str() regardless of the
input.
Signed-off-by: Pavel Roskin
---
scripts/kconfig/menu.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
index a26cc5d..72c9dba 100644
--- a/scripts/kconfi
be no behavior change in get_prompt_str() regardless of the
input.
Signed-off-by: Pavel Roskin pro...@gnu.org
---
scripts/kconfig/menu.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
index a26cc5d..72c9dba 100644
--- a/scripts
trusted.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
it is to be
trusted.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
should unset the low_latency flag as soon as DMA fails? There
are two flags, one is state->uart_port->flags and the other is
port->low_latency. I guess we need to unset both.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
and the other is
port-low_latency. I guess we need to unset both.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
ulator, decompression could be slow.
If the kernel runs in a virtual machine, the kernel would need to be
decompressed separately for every virtual machine. Reading from the
disk would be done only once if several virtual machines are started in
a short period of time.
--
Regards,
Pavel Roskin
--
T
machine, the kernel would need to be
decompressed separately for every virtual machine. Reading from the
disk would be done only once if several virtual machines are started in
a short period of time.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
pression" could be a symlink. Alternatively, the "." could be
included in other suffixes, the uncompressed suffix would be empty and
the compression would be an empty statement.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
. Then the
compression could be a symlink. Alternatively, the . could be
included in other suffixes, the uncompressed suffix would be empty and
the compression would be an empty statement.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On Thu, 17 Oct 2013 13:26:47 +0100
Chris Wilson wrote:
> On Wed, Oct 16, 2013 at 08:12:35PM -0400, Pavel Roskin wrote:
> > The amount of data wanted by the userspace caller is encoded in the
> > ioctl number. Generic drm ioctls were ignoring it.
> >
> > As a resul
On Thu, 17 Oct 2013 13:26:47 +0100
Chris Wilson ch...@chris-wilson.co.uk wrote:
On Wed, Oct 16, 2013 at 08:12:35PM -0400, Pavel Roskin wrote:
The amount of data wanted by the userspace caller is encoded in the
ioctl number. Generic drm ioctls were ignoring it.
As a result, Intel Xorg
-by: Pavel Roskin
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/drm_drv.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index e572dd2..8a1c721 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
-by: Pavel Roskin pro...@gnu.org
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/drm_drv.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index e572dd2..8a1c721 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm
On Wed, 2 Oct 2013 16:41:04 +0200
David Herrmann wrote:
> Tested-by: Pavel Roskin
Tested indeed, on ThinkPad W530 with 32-bit and 64-bit kernels with
Intel and NVidia graphics enabled.
> Sorry for the delay, but I was in the US for the last 2 weeks and
> this is really no major is
On Wed, 2 Oct 2013 16:41:04 +0200
David Herrmann dh.herrm...@gmail.com wrote:
Tested-by: Pavel Roskin pro...@gnu.org
Tested indeed, on ThinkPad W530 with 32-bit and 64-bit kernels with
Intel and NVidia graphics enabled.
Sorry for the delay, but I was in the US for the last 2 weeks
em but not in the linux-firmware tree.
The kernel doesn't know whether the firmware is missing due to
licensing issues or due to misconfiguration. The kernel cannot know
that. And I don't think the kernel should include as much information
as the MISSING file would include.
--
Regards,
Pavel Ro
-firmware tree.
The kernel doesn't know whether the firmware is missing due to
licensing issues or due to misconfiguration. The kernel cannot know
that. And I don't think the kernel should include as much information
as the MISSING file would include.
--
Regards,
Pavel Roskin
--
To unsubscribe
anything.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
if I mishandled anything.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
. -ENOENT is both magic and negative :)
I tend to think now that iterate_fd() should be rewritten before it's too
late and all its current users should be cross-checked against the
code prior to the introduction of iterate_fd().
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send
the crazy logics?
I agree. -ENOENT is both magic and negative :)
I tend to think now that iterate_fd() should be rewritten before it's too
late and all its current users should be cross-checked against the
code prior to the introduction of iterate_fd().
--
Regards,
Pavel Roskin
--
To unsubscribe from
Quoting Pavel Roskin :
Hello, Al!
I have noticed that Mozilla Firefox gets stuck for seconds or minutes
on some sites, in particular on Facebook with Linux 3.7-rc1 and newer
mainline kernels. Disabling flash plugin fixes the delays.
This is a Fedora 17 system with SELinux enabled, on x86_64
Quoting Pavel Roskin pro...@gnu.org:
Hello, Al!
I have noticed that Mozilla Firefox gets stuck for seconds or minutes
on some sites, in particular on Facebook with Linux 3.7-rc1 and newer
mainline kernels. Disabling flash plugin fixes the delays.
This is a Fedora 17 system with SELinux
ior.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
is
sufficient to restore the correct behavior.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
On Tue, 16 Oct 2012 00:48:53 +0100
Al Viro wrote:
> On Mon, Oct 15, 2012 at 07:40:08PM -0400, Pavel Roskin wrote:
> > On Tue, 16 Oct 2012 00:27:05 +0100
> > Al Viro wrote:
> >
> > > I think I understand what's going on there. Add
> > > fput(files[0])
On Tue, 16 Oct 2012 00:48:53 +0100
Al Viro v...@zeniv.linux.org.uk wrote:
On Mon, Oct 15, 2012 at 07:40:08PM -0400, Pavel Roskin wrote:
On Tue, 16 Oct 2012 00:27:05 +0100
Al Viro v...@zeniv.linux.org.uk wrote:
I think I understand what's going on there. Add
fput(files[0]) after
ow! No more hang on login!
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon, 15 Oct 2012 22:51:27 +0100
Al Viro wrote:
> On Mon, Oct 15, 2012 at 05:14:37PM -0400, Pavel Roskin wrote:
> > Hello!
> >
> > I tried the current mainline Linux on Fedora 16 x64_64 and found
> > that I cannot login in gdm. I'm using gdm with LXDE. Afte
On Mon, 15 Oct 2012 22:51:27 +0100
Al Viro v...@zeniv.linux.org.uk wrote:
On Mon, Oct 15, 2012 at 05:14:37PM -0400, Pavel Roskin wrote:
Hello!
I tried the current mainline Linux on Fedora 16 x64_64 and found
that I cannot login in gdm. I'm using gdm with LXDE. After a few
minutes
working now! No more hang on login!
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
" name or
stick with the semaphore functionality if it's really needed).
--
Regards,
Pavel Roskin
--
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 rea
with the semaphore functionality if it's really needed).
--
Regards,
Pavel Roskin
--
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
because it would break existing modprobe
configuration files that bind ndiswrapper to specific devices.
Please let's not turn it into another empty discussion.
I represent only myself and I'm not a lawyer.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe
It's an experimental option and it's not generally recommended
Signed-off-by: Pavel Roskin <[EMAIL PROTECTED]>
---
init/Kconfig |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index dcef8b5..a998a13 100644
--- a/init/Kconfig
+++
It's an experimental option and it's not generally recommended
Signed-off-by: Pavel Roskin [EMAIL PROTECTED]
---
init/Kconfig |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index dcef8b5..a998a13 100644
--- a/init/Kconfig
+++ b/init/Kconfig
because it would break existing modprobe
configuration files that bind ndiswrapper to specific devices.
Please let's not turn it into another empty discussion.
I represent only myself and I'm not a lawyer.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux
ss if will just stay in sync
with the upstream.
Many thanks for pushing it into the kernel.
--
Regards,
Pavel Roskin
--
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/m
with the upstream.
Many thanks for pushing it into the kernel.
--
Regards,
Pavel Roskin
--
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
Revert 0aa5bd52d0c49ca56d24584c646e6544ccbb3dc9, which disallowed
ndiswrapper to use GPL-only symbols.
Add comments why ndiswrapper and driverloader are tainted to avoid
similar mistakes in the future.
Signed-off-by: Pavel Roskin <[EMAIL PROTECTED]>
---
kernel/module.c |7 ++-
1
Revert 0aa5bd52d0c49ca56d24584c646e6544ccbb3dc9, which disallowed
ndiswrapper to use GPL-only symbols.
Add comments why ndiswrapper and driverloader are tainted to avoid
similar mistakes in the future.
Signed-off-by: Pavel Roskin [EMAIL PROTECTED]
---
kernel/module.c |7 ++-
1 files
logy would be running a non-free program in a free emulator.
I don't have any issues with ndiswrapper. If anyone does, they should
write to FSF, or maybe to FSF Europe if the concern are about European
laws.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscr
issues with ndiswrapper. If anyone does, they should
write to FSF, or maybe to FSF Europe if the concern are about European
laws.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Quoting Andi Kleen <[EMAIL PROTECTED]>:
Pavel Roskin <[EMAIL PROTECTED]> writes:
*/
@@ -162,6 +163,7 @@ const char *print_tainted(void)
if (tainted) {
snprintf(buf, sizeof(buf), "Tainted: %c%c%c%c%c%c%c%c",
tainted &
Add comments to show the difference between driverloader and
ndiswrapper.
Signed-off-by: Pavel Roskin <[EMAIL PROTECTED]>
---
include/linux/kernel.h |1 +
kernel/module.c|5 -
kernel/panic.c |2 ++
3 files changed, 7 insertions(+), 1 deletions(-)
diff --g
stays in memory, just like it does when a proprietary program runs on
top of the Linux kernel. Memory dumps might be illegal to distribute
though.
I'm not a lawyer and the above is not a legal advice. I don't represent
Free Software Foundation.
--
Regards,
Pavel Roskin
--
To unsubscribe from this
"struct module". And I think we really don't want modules tainting
and untainting themselves by changing THIS_MODULE->taints. It's a
Pandora's box that's better kept closed.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
ithout checking the entire
> history of LWN stories beforehand. I'm going to the gym to escape :)
I'm actually so relieved that it has been mistake, just like it was the
last time. Good luck!
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linu
he author fails to make
the necessary updates for the next kernel for whatever reason, somebody
will fork it and make such updates.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More major
On Wed, 2008-01-30 at 00:57 +0200, Adrian Bunk wrote:
> On Tue, Jan 29, 2008 at 04:22:45PM -0500, Pavel Roskin wrote:
> > Hello!
> >
> > It have come to my attention that a patch has been committed to the
> > kernel with the explicit purpose of tainting ndiswrap
On Tue, 2008-01-29 at 17:27 -0500, [EMAIL PROTECTED] wrote:
> On Tue, 29 Jan 2008 16:22:45 EST, Pavel Roskin said:
> > Hello!
> >
> > It have come to my attention that a patch has been committed to the
> > kernel with the explicit purpose of tainting ndiswrapper - the
a completely free OS; take it
away and see less users, less testers and less reverse engineering
efforts
--
Regards,
Pavel Roskin
--
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.
a completely free OS; take it
away and see less users, less testers and less reverse engineering
efforts
--
Regards,
Pavel Roskin
--
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 Tue, 2008-01-29 at 17:27 -0500, [EMAIL PROTECTED] wrote:
On Tue, 29 Jan 2008 16:22:45 EST, Pavel Roskin said:
Hello!
It have come to my attention that a patch has been committed to the
kernel with the explicit purpose of tainting ndiswrapper - the kernel
module allowing Windows NDIS
On Wed, 2008-01-30 at 00:57 +0200, Adrian Bunk wrote:
On Tue, Jan 29, 2008 at 04:22:45PM -0500, Pavel Roskin wrote:
Hello!
It have come to my attention that a patch has been committed to the
kernel with the explicit purpose of tainting ndiswrapper - the kernel
module allowing Windows
reason, somebody
will fork it and make such updates.
--
Regards,
Pavel Roskin
--
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 it has been mistake, just like it was the
last time. Good luck!
--
Regards,
Pavel Roskin
--
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
modules tainting
and untainting themselves by changing THIS_MODULE-taints. It's a
Pandora's box that's better kept closed.
--
Regards,
Pavel Roskin
--
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
is not a legal advice. I don't represent
Free Software Foundation.
--
Regards,
Pavel Roskin
--
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
the difference between driverloader and
ndiswrapper.
Signed-off-by: Pavel Roskin [EMAIL PROTECTED]
---
include/linux/kernel.h |1 +
kernel/module.c|5 -
kernel/panic.c |2 ++
3 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/include/linux/kernel.h b
Quoting Andi Kleen [EMAIL PROTECTED]:
Pavel Roskin [EMAIL PROTECTED] writes:
*/
@@ -162,6 +163,7 @@ const char *print_tainted(void)
if (tainted) {
snprintf(buf, sizeof(buf), Tainted: %c%c%c%c%c%c%c%c,
tainted TAINT_PROPRIETARY_MODULE ? 'P
Linux page flags.
Last but not least, mmiotrace should be useful for free drivers in the
first place to have a legitimate reason to be in the kernel.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Wed, 2008-01-09 at 20:26 +, Christoph Hellwig wrote:
> On Wed, Jan 09, 2008 at 03:24:16PM -0500, Pavel Roskin wrote:
> > I just assumed (wrongly, as it seems) that the API change didn't remove
> > any useful functionality.
>
> No, this was exactly the correct ass
On Thu, 2008-01-10 at 06:58 +1100, Benjamin Herrenschmidt wrote:
> On Wed, 2008-01-09 at 18:21 +, Christoph Hellwig wrote:
> > On Wed, Jan 09, 2008 at 01:18:44PM -0500, Pavel Roskin wrote:
> > > notification without patching the kernel. But if no such solution is
> &g
ll be able to implement fault
notification without patching the kernel. But if no such solution is
found, I would also support reverting the patch that removed fault
notifiers on i386.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
the kernel. But if no such solution is
found, I would also support reverting the patch that removed fault
notifiers on i386.
--
Regards,
Pavel Roskin
--
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
On Thu, 2008-01-10 at 06:58 +1100, Benjamin Herrenschmidt wrote:
On Wed, 2008-01-09 at 18:21 +, Christoph Hellwig wrote:
On Wed, Jan 09, 2008 at 01:18:44PM -0500, Pavel Roskin wrote:
notification without patching the kernel. But if no such solution is
found, I would also support
On Wed, 2008-01-09 at 20:26 +, Christoph Hellwig wrote:
On Wed, Jan 09, 2008 at 03:24:16PM -0500, Pavel Roskin wrote:
I just assumed (wrongly, as it seems) that the API change didn't remove
any useful functionality.
No, this was exactly the correct assumption. Out of tree modules
page flags.
Last but not least, mmiotrace should be useful for free drivers in the
first place to have a legitimate reason to be in the kernel.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
_len; /* Lenght of result */
> + int scan_len; /* Length of result */
> };
>
> #ifdef ORINOCO_DEBUG
Acked-by: Pavel Roskin <[EMAIL PROTECTED]>
Actually, I don't think such minor comment fixes need to be reviewed by
the maintainers. Thanks
*/
+ int scan_len; /* Length of result */
};
#ifdef ORINOCO_DEBUG
Acked-by: Pavel Roskin [EMAIL PROTECTED]
Actually, I don't think such minor comment fixes need to be reviewed by
the maintainers. Thanks anyway.
--
Regards,
Pavel Roskin
--
To unsubscribe from this list: send
ol, so the
improved code could be contributed back there.
I guess if there is no simple answer, I'll have to try a few crazy
ideas. If nothing works, the fault handler chain could be reinstated,
perhaps as a separate configuration option.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list
preciated.
--
Regards,
Pavel Roskin
-
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/
.
--
Regards,
Pavel Roskin
-
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/
the
improved code could be contributed back there.
I guess if there is no simple answer, I'll have to try a few crazy
ideas. If nothing works, the fault handler chain could be reinstated,
perhaps as a separate configuration option.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send
describe
v2.6.23-4223-g65a6ec0
Format is: last tag - # commits since last tag - id of HEAD commit
I don't see how I can use it in preprocessor conditions.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
-g65a6ec0
Format is: last tag - # commits since last tag - id of HEAD commit
I don't see how I can use it in preprocessor conditions.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Tue, 2007-10-16 at 22:41 -0400, Rik van Riel wrote:
> On Tue, 16 Oct 2007 22:22:43 -0400
> Pavel Roskin <[EMAIL PROTECTED]> wrote:
>
> > I'm trying to keep some external drivers up to date with the kernel,
> > and the first two weeks after the release is the worst
On Tue, 2007-10-16 at 22:34 -0400, Dave Jones wrote:
> On Tue, Oct 16, 2007 at 10:22:43PM -0400, Pavel Roskin wrote:
>
> > It would be nice to establish a rule to increment the version number
> > immediately after the kernel release and have a suffix to indicate that
> &g
t the version number
immediately after the kernel release and have a suffix to indicate that
it's a pre-rc version. "rc0" is my personal favorite.
It would also be helpful for other repositories, as it would indicate
whether any post-release changes have been merged in.
--
Regards,
Pavel
after the kernel release and have a suffix to indicate that
it's a pre-rc version. rc0 is my personal favorite.
It would also be helpful for other repositories, as it would indicate
whether any post-release changes have been merged in.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list
On Tue, 2007-10-16 at 22:34 -0400, Dave Jones wrote:
On Tue, Oct 16, 2007 at 10:22:43PM -0400, Pavel Roskin wrote:
It would be nice to establish a rule to increment the version number
immediately after the kernel release and have a suffix to indicate that
it's a pre-rc version. rc0
On Tue, 2007-10-16 at 22:41 -0400, Rik van Riel wrote:
On Tue, 16 Oct 2007 22:22:43 -0400
Pavel Roskin [EMAIL PROTECTED] wrote:
I'm trying to keep some external drivers up to date with the kernel,
and the first two weeks after the release is the worst time for me.
Consider
ing used, maybe -1, but hardly anything else.
Maybe you could add the code printing the value and then get some
statics on the actual Linux kernel to see which values are common and
which are not?
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe linu
you could add the code printing the value and then get some
statics on the actual Linux kernel to see which values are common and
which are not?
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Quoting Joe Perches <[EMAIL PROTECTED]>:
On Tue, 2007-08-28 at 13:15 -0400, Pavel Roskin wrote:
NAK. Please also add airport*, spectrum* and hermes* in the same
directory.
Here's what I have now:
ORINOCO/AIRPORT/SPECTRUM/HERMES WIRELESS DRIVERS
P: Pavel Roskin
M: [EMAIL PRO
NERS
> @@ -3463,6 +3463,7 @@ L: [EMAIL PROTECTED]
> L: [EMAIL PROTECTED]
> W: http://www.nongnu.org/orinoco/
> S: Maintained
> +F: drivers/net/wireless/orinoco*
NAK. Please also add airport*, spectrum* and hermes* in the same
directory.
Sorry for delay (due to vacation).
PROTECTED]
L: [EMAIL PROTECTED]
W: http://www.nongnu.org/orinoco/
S: Maintained
+F: drivers/net/wireless/orinoco*
NAK. Please also add airport*, spectrum* and hermes* in the same
directory.
Sorry for delay (due to vacation).
--
Regards,
Pavel Roskin
-
To unsubscribe from this list
Quoting Joe Perches [EMAIL PROTECTED]:
On Tue, 2007-08-28 at 13:15 -0400, Pavel Roskin wrote:
NAK. Please also add airport*, spectrum* and hermes* in the same
directory.
Here's what I have now:
ORINOCO/AIRPORT/SPECTRUM/HERMES WIRELESS DRIVERS
P: Pavel Roskin
M: [EMAIL PROTECTED
am rules. This time the message it not
forwarded. Instead, it can be found on my website with full headers:
http://80211libre.org/mvistaspam.txt
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
the message it not
forwarded. Instead, it can be found on my website with full headers:
http://80211libre.org/mvistaspam.txt
--
Regards,
Pavel Roskin
-
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
ardware just in case. If you have further questions, please
post them to [EMAIL PROTECTED]
--
Regards,
Pavel Roskin
-
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/majo
. If you have further questions, please
post them to [EMAIL PROTECTED]
--
Regards,
Pavel Roskin
-
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
e later is the case.
I wish I could submit a patch for the documentation, but I still don't
understand much of the theory. Still, I was able to interpret the error
messages in a way that allows me to fix the locking issues in some
drivers.
--
Regards,
Pavel Roskin
-
To unsubscribe from t
I could submit a patch for the documentation, but I still don't
understand much of the theory. Still, I was able to interpret the error
messages in a way that allows me to fix the locking issues in some
drivers.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line unsubscribe
of wrinkles in the standalone build
system are irrelevant to the kernel interation.
--
Regards,
Pavel Roskin
-
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/
to the kernel interation.
--
Regards,
Pavel Roskin
-
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/
1 - 100 of 212 matches
Mail list logo
