This patch stops "modpost" from issuing erroneous modpost warnings on ARM
builds, which it's been doing since since maybe last summer. A canonical
example would be driver method table entries:
WARNING: - Section mismatch: reference to .exit.text:_remove
from .data after '$d' (at
Hello James,
I re-submitted the patch yesterday with the "space" issue fixed
(adhering to coding guideline).
I will check for alternative to calculate the time driver have
been sending host busy to OS. Will check with time_before() as you have
suggested.
Throttling from
Hi,
I have a very basic query regarding kernel porting on different
boards. I understand that even if two boards have the very same
processor core (say MIPS 4KE), we need to port linux for them
seperately. I have heard things like it is because of certain "board
level differences", I need to
On 2/16/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
No, that's the FSF marketing fluff you've been taught to recite.
In the context of the Linux kernel, I'm referring to the original reason
why Linus chose the GPL for the Linux kernel.
Great.. The reason why Greg KH, the guy who wrote the bit
Eric W. Biederman wrote:
> Len Brown <[EMAIL PROTECTED]> writes:
>
>> e1000 faults in 2.6.20-git, while 2.6.20 worked fine.
>>
>> System is a D875PBZ with LOM.
>>
>> clues?
>
> I'm guessing this is an old bug found by the following bit of
> debug coded added into since v2.6.20
>
> +#ifdef
On 2/15/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
Michael K. Edwards wrote:
> Bzzzt. The whole point of the GPL is to "guarantee your freedom to
> share and change free software--to make sure the software is free for
> all its users."
No, that's the FSF marketing fluff you've been taught to
Linus Torvalds wrote:
On Thu, 15 Feb 2007, Jeff Garzik wrote:
diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
index db185f3..d51f0f1 100644
--- a/arch/ia64/Kconfig
+++ b/arch/ia64/Kconfig
@@ -22,6 +22,7 @@ config IA64
config 64BIT
bool
+ select ATA_NONSTANDARD if ATA
On 2/15/07, Scott Preece <[EMAIL PROTECTED]> wrote:
On 2/15/07, v j <[EMAIL PROTECTED]> wrote:
> So far I have heard nothing but, "if you don't contribute, screw you."
> All this is fine. Just say so. Make it black and white. Make it
> perfectly clear what is and isn't legal. If we can't load
On Thu, Feb 15, 2007 at 05:27:20PM -0800, Andrew Morton wrote:
> No, icc surely supports attribute(packed). My point is that we shouldn't
> rely upon the gcc info file for this, because other compilers can (or
> could) be used to build the kernel.
>
> So it would be safer if the C spec said (or
On 2/15/07, Greg Trounson <[EMAIL PROTECTED]> wrote:
I wasn't disputing legal problems with proprietary drivers nor suggesting
people ignore
the issue. I was trying to make the point that Linux is adversely affected
when lots of
users, proprietary developers or otherwise, abandon Linux, and
On Thu, 15 Feb 2007 20:33:48 -0500 Mathieu Desnoyers wrote:
> Linux Kernel Markers - Documentation
>
> Here is some documentation explaining what is/how to use the Linux
> Kernel Markers.
>
> Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
>
> --- /dev/null
> +++
On 2/15/07, Gene Heskett <[EMAIL PROTECTED]> wrote:
This definition seems to be a bit like nailing jelly to a tree in that so
far only one companies legal dept has pursued this to the point of
actually getting a court verdict rendered. That was the German ruling a
link was given to earlier in
On Thu, 15 Feb 2007 14:46:34 -0500, Jan Engelhardt
<[EMAIL PROTECTED]> wrote:
On Feb 15 2007 21:38, Andi Kleen wrote:
Also I would expect your design to be slow for metadata read intensive
workloads. E.g. have you tried to boot a root partition with dual fs?
That's a very important IO
Linux Kernel Markers - Documentation
Here is some documentation explaining what is/how to use the Linux
Kernel Markers.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- /dev/null
+++ b/Documentation/marker.txt
@@ -0,0 +1,130 @@
+Using the Linux Kernel Markers
+
+
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Sun, 11 Feb 2007 15:03:22 -0500 Mathieu Desnoyers <[EMAIL PROTECTED]>
> wrote:
>
> > You will find, in the following posts, the latest revision of the Linux
> > Kernel
> > Markers.
>
>
>
I guess the header of include/linux/marker.h should go
On Fri, 16 Feb 2007 00:43:17 +
Ralf Baechle <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 15, 2007 at 03:38:23PM -0800, Andrew Morton wrote:
>
> > hm. So if I have
> >
> > struct bar {
> > unsigned long b;
> > } __attribute__((packed));
> >
> > struct foo {
> >
On Thu, 15 Feb 2007 19:58:04 -0500
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> > >
> > > --- a/Makefile
> > > +++ b/Makefile
> > > @@ -309,7 +309,8 @@ AFLAGS_KERNEL =
> > > LINUXINCLUDE:= -Iinclude \
> > > $(if $(KBUILD_SRC),-Iinclude2 -I$(srctree)/include) \
> > >
On Thu, 15 Feb 2007 19:55:29 -0500
Andres Salomon <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > On Thu, 15 Feb 2007 05:08:21 -0500
> > Andres Salomon <[EMAIL PROTECTED]> wrote:
> >
> >> Initial framework for disabling PS/2 protocol extensions. The current
> >> protocols can only be
On Thu, 15 Feb 2007, Scott Preece wrote:
On 2/15/07, Miguel Ojeda <[EMAIL PROTECTED]> wrote:
Stupid, maybe. But some people just don't want closed-source
projects/companies like yours using their free work, without any kind
of feedback. Some others don't care, but they could in the future, as
I've built a tool with the goal of logging mmio writes and reads by
device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.
I'd like to add support for recording a time stamp on each read and
write. Unfortunately, I am not sure which clock api I should use.
I had a look at blktrace
On 2/15/07, Geert Uytterhoeven <[EMAIL PROTECTED]> wrote:
On Thu, 15 Feb 2007, v j wrote:
Personally, I see no real difference between EXPORT_SYMBOL and
EXPORT_SYMBOL_GPL.
If you derive from GPL'ed code, your code is a derived work.
---
I agree with you that there's no difference in law,
On Thu, 15 Feb 2007 19:37:39 -0500
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> > For what reason was that change made?
> >
>
> It was made so that we can use the markers in C code without actually
> including marker.h everywhere. I am sure someone has a better way to do
> it : I would be
On Thu, 15 Feb 2007 13:26:29 -0600
Marc St-Jean <[EMAIL PROTECTED]> wrote:
> + status = *(volatile u32 *)up->port.private_data;
It distresses me that this patch uses a variable which this patch
doesn't initialise anywhere. It isn't complete.
The sub-driver code whch sets up
On 2/15/07, Miguel Ojeda <[EMAIL PROTECTED]> wrote:
Stupid, maybe. But some people just don't want closed-source
projects/companies like yours using their free work, without any kind
of feedback. Some others don't care, but they could in the future, as
it is their code, and that is your risk.
From: Randy Dunlap <[EMAIL PROTECTED]>
Add TAINT_USER description to Tainted flags in oops-tracing.txt.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
Documentation/oops-tracing.txt |3 +++
1 file changed, 3 insertions(+)
--- linux-2.6.20-git9.orig/Documentation/oops-tracing.txt
+++
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Thu, 15 Feb 2007 19:23:47 -0500
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > sparse chokes on arch/i386/kernel/i8253.c
> >
> > Here is a marker fix that puts the correct -i include/linux/marker.h in
> > the top level Makefile so sparse
On 2/15/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
But so what? How will that hurt *Linux*? If the Embedded developers
don't contribute changes back, it doesn't hurt us any if they go away
and start paying $$$ to VxWorks instead of using Linux for free.
---
Well, this is somewhat
Andrew Morton wrote:
> On Thu, 15 Feb 2007 05:08:21 -0500
> Andres Salomon <[EMAIL PROTECTED]> wrote:
>
>> Initial framework for disabling PS/2 protocol extensions. The current
>> protocols can only be disabled if CONFIG_EMBEDDED is selected. No
>> source files are changed, merely build stuff.
On Thu, 15 Feb 2007 05:08:21 -0500
Andres Salomon <[EMAIL PROTECTED]> wrote:
> Initial framework for disabling PS/2 protocol extensions. The current
> protocols can only be disabled if CONFIG_EMBEDDED is selected. No
> source files are changed, merely build stuff.
ugleee. What benefit do we
Rui Nuno Capela (me) wrote:
>
> I have terrible news: 2.6.20-rt5 does not boot at all on a couple
> machines I was brave enough to try -- a [EMAIL PROTECTED] SMP/HT desktop, and
> a
> Core2 Duo [EMAIL PROTECTED] laptop. For the first case I could capture the
> following dump via serial console:
On Thu, Feb 15, 2007 at 03:38:23PM -0800, Andrew Morton wrote:
> hm. So if I have
>
> struct bar {
> unsigned long b;
> } __attribute__((packed));
>
> struct foo {
> unsigned long u;
> struct bar b;
> };
>
> then the compiler
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Thu, 15 Feb 2007 17:46:56 -0500
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > > Me too. It's due to the linux-kernel-markers patches. Mathieu, can you
> > > take a look please?
> >
> > I will give a deeper look in sparse, but I should say
On Thu, 15 Feb 2007 19:23:47 -0500
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> sparse chokes on arch/i386/kernel/i8253.c
>
> Here is a marker fix that puts the correct -i include/linux/marker.h in
> the top level Makefile so sparse works correctly. The tricky part is to
> keep the kernel
> I must have missed something, who is trying to coerce people into not
> exercising the rights the GPL gave them?
Anyone who claims that it is unlawful to "circumvent" the EXPORT_SYMBOL_GPL
stuff. Anyone who adds copyright or license enforcement mechansims to GPL'd
code and distributes the
Michael K. Edwards wrote:
On 2/15/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
v j wrote:
> So far I have heard nothing but, "if you don't contribute, screw you."
> All this is fine. Just say so. Make it black and white. Make it
It is black and white in copyright law and the GPL.
The /whole
Lee Revell wrote:
On 2/15/07, Greg Trounson <[EMAIL PROTECTED]> wrote:
Theodore Tso wrote:
> On Wed, Feb 14, 2007 at 10:27:10PM -0800, v j wrote:
>> You are right. I have not contributed anything to Linux. Except one
>> small patch to the MTD code. However, I don't think that is the point
>>
On 2/15/07, Stuart MacDonald <[EMAIL PROTECTED]> wrote:
Linus does allow for one exception; drivers written for other OSes
that happen to compile for Linux as well. I believe this is the POSIX
exception mentioned elsethread. However, from your description of
requiring GPL-only symbols, I'm
Arnd Bergmann wrote:
On Thursday 15 February 2007 00:52, Carl Love wrote:
--- linux-2.6.20-rc1.orig/arch/powerpc/oprofile/Kconfig 2007-01-18
16:43:14.0 -0600
+++ linux-2.6.20-rc1/arch/powerpc/oprofile/Kconfig 2007-02-13
19:04:46.271028904 -0600
@@ -7,7 +7,8 @@
config
On Thursday 15 February 2007 22:50, Paul E. McKenney wrote:
> Is this 1.5ms with interrupts disabled? This time period is problematic
> from a realtime perspective if so -- need to be able to preempt.
No, interrupts should be enabled here. Still, 1.5ms is probably a little
too long without a
On Thursday 15 February 2007 12:34, [EMAIL PROTECTED] wrote:
> On Wed, 14 Feb 2007 22:14:53 PST, Andreas Gruenbacher said:
> > I agree, that's really what should happen. We solve this by marking
> > modules as supported, partner supported, or unsupported, but in an
> > "insecure" way, so partners
sparse chokes on arch/i386/kernel/i8253.c
Here is a marker fix that puts the correct -i include/linux/marker.h in
the top level Makefile so sparse works correctly. The tricky part is to
keep the kernel compiling correctly with a kernel build directory
different from the kernel source tree too.
Andrew Morton wrote:
On Thu, 15 Feb 2007 09:49:15 -0600
Corey Minyard <[EMAIL PROTECTED]> wrote:
So I see the following options besides what's already there:
1) add asm/kdebug.h and DIE_NMI_POST to everything that might have an
IPMI implementation.
2) use CONFIG_X86 to tell if NMI will
Eric W. Biederman napisał(a):
> When enhancing do_shmat I forgot to take into account that shm_lock
> is a spinlock, and was allocating memory with the lock held.
>
> This patch fixes that by grabbing a reference to the dentry and
> mounts of shm_file before we drop the shm_lock and then
On 2/15/07, Greg Trounson <[EMAIL PROTECTED]> wrote:
Theodore Tso wrote:
> On Wed, Feb 14, 2007 at 10:27:10PM -0800, v j wrote:
>> You are right. I have not contributed anything to Linux. Except one
>> small patch to the MTD code. However, I don't think that is the point
>> here. I am perfectly
On Fri, 16 Feb 2007 00:24:35 +0100
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Andrew Morton napisa__(a):
> > On Thu, 15 Feb 2007 15:37:20 +0100
> > Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> >
> >> Andrew Morton napisa__(a):
> >>> Temporarily at
> >>>
> >>>
Eric W. Biederman napisał(a):
> When enhancing do_shmat I forgot to take into account that shm_lock
> is a spinlock, and was allocating memory with the lock held.
>
> This patch fixes that by grabbing a reference to the dentry and
> mounts of shm_file before we drop the shm_lock and then
Am 15.02.2007 22:56 schrieb Adrian Bunk:
> This patch fixes the following compile error:
>
> <-- snip -->
>
> ...
> LD drivers/isdn/gigaset/built-in.o
> drivers/isdn/gigaset/ser_gigaset.o: In function `gigaset_m10x_send_skb':
> (.text+0xe50): multiple definition of
Andrew Morton wrote:
> hm. So if I have
>
> struct bar {
> unsigned long b;
> } __attribute__((packed));
>
> struct foo {
> unsigned long u;
> struct bar b;
> };
>
> then the compiler can see that foo.b.b is well-aligned,
On Tue, 2007-02-06 at 14:11 -0800, Sumant Patro wrote:
> Checks added in megasas_queue_command to know if FW is able to process
> commands within timeout period. If number of retries is 2 or greater,
> the driver stops sending cmd to FW. IO is resumed if pending cmd count
> reduces to 16 or 5
Theodore Tso wrote:
On Wed, Feb 14, 2007 at 10:27:10PM -0800, v j wrote:
You are right. I have not contributed anything to Linux. Except one
small patch to the MTD code. However, I don't think that is the point
here. I am perfectly willing to live with the way Linux is today. I am
telling you
Jiri Slaby napsal(a):
[...]
unify queue_delayed_work and queue_delayed_work_on fix
Oh sorry, the name should be
make queue_delayed_work() friendly to flush_fork() fix
Since cwq->wq is unset for other than singlethread_cpu when singlethread
workqueue was created, an oops occurs during bootup.
When enhancing do_shmat I forgot to take into account that shm_lock
is a spinlock, and was allocating memory with the lock held.
This patch fixes that by grabbing a reference to the dentry and
mounts of shm_file before we drop the shm_lock and then performing
the memory allocations.
This is
On 2/15/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
v j wrote:
> So far I have heard nothing but, "if you don't contribute, screw you."
> All this is fine. Just say so. Make it black and white. Make it
It is black and white in copyright law and the GPL.
The /whole point/ of the GPL is to funnel
Am 15.02.2007 22:56 schrieb Adrian Bunk:
> Advanced Mathematics, lesson 1:
> 101 != 105
Ouch. Sorry. Thanks for catching that one.
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Acked-by: Tilman Schmidt <[EMAIL PROTECTED]>
> ---
> --- linux-2.6.20-mm1/drivers/isdn/gigaset/Makefile.old
On Fri, Feb 16, 2007 at 01:49:45AM +0200, S.Çağlar Onur wrote:
> Hi;
>
> 15 Şub 2007 Per tarihinde şunları yazmıştınız:
> > Location:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/bunk/linux-2.6.16.y/testing/
> >
> > git tree:
> >
On Feb 15, 2007, at 3:32 PM, Ananiev, Leonid I wrote:
If EIOCBRETRY then generic_file_aio_write() will be recalled for the
same iocb.
Only if kick_iocb() is called. It won't be called if i_i_p2_r() was
the only thing to return -EIOCBRETRY.
It is not need to call kick_iocb()
for
> >Also many storage subsystems have some internal parallelism
> >in writing (e.g. a RAID can write on different disks in parallel for
> >a single partition) so i'm not sure your distinction is that useful.
> >
> But we are talking about a different case. What I have said is that if you
> use two
Andrew Morton wrote:
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-mm1/
[...]
> +unify-queue_delayed_work-and-queue_delayed_work_on.patch
I'm getting oops in delayed_work_timer_fn, since cwq->wq is NULL and accessed
there. The patch below fixes the problem for me.
--
unify
On Thu, 15 Feb 2007, Linus Torvalds wrote:
>
> Ok, this is just _strange_.
Btw, I did pull, but I still think we shouldn't do those kinds of strange
Kconfig file games.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Zachary Amsden wrote:
> So Rusty, Chris, Jeremy, any objections to killing udelay() and
> friends in paravirt-ops? It would simplify things a bit. The only
> thing we lose is a slightly faster boot time in the 100% emulated
> device case. I'm ok with losing that. Even the PIT fast paths don't
On Fri, 16 Feb 2007 16:41:59 +
Frederik Deweerdt <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 15, 2007 at 05:14:08AM -0800, Andrew Morton wrote:
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.20-mm1/
> >
> Hi,
>
> It appears that the pcim_iomap_regions() function doesn't
Hi;
15 Şub 2007 Per tarihinde şunları yazmıştınız:
> Location:
> ftp://ftp.kernel.org/pub/linux/kernel/people/bunk/linux-2.6.16.y/testing/
>
> git tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
>
>
> Changes since 2.6.16.40:
What about CVE-2006-6333,
Hi!
> >You know it is ugly. Alan demonstrated it even hurts performance, but
> >being ugly is the main problem.
> >
>
> No argument with that. Well, we're ok with dropping it. Actually,
> reverting the entire set of udelay changes now seems wise. The same
>bug
Good, thanks.
Sam Ravnborg wrote:
> On Thu, Feb 15, 2007 at 01:19:12PM -0800, Jeremy Fitzhardinge wrote:
>
>> No need to use -traditional for processing asm in i386/kernel/
>>
>> Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
>>
>
> Any possibility that you could 'fix' the three remaining
> uses
On Thu, 15 Feb 2007, Jeff Garzik wrote:
>
> diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
> index db185f3..d51f0f1 100644
> --- a/arch/ia64/Kconfig
> +++ b/arch/ia64/Kconfig
> @@ -22,6 +22,7 @@ config IA64
>
> config 64BIT
> bool
> + select ATA_NONSTANDARD if ATA
>
On Thu, 15 Feb 2007 17:46:56 -0500
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> > Me too. It's due to the linux-kernel-markers patches. Mathieu, can you
> > take a look please?
>
> I will give a deeper look in sparse, but I should say up front that I
> add this to the root build tree
On Feb 15, 2007, at 4:33 PM, Sam Ravnborg wrote:
On Thu, Feb 15, 2007 at 01:18:52PM -0600, Kumar Gala wrote:
I was wondering if there was some way to make a Kconfig menu either
be just a menu or a choice depending on another bool being set or
not.
What I'm trying to accomplish is if
Yes I can make it boolean.
Will change it in a future patch submission.
Thanks,
Sumant
-Original Message-
From: Richard Knutsson [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 15, 2007 12:10 AM
To: Patro, Sumant
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
linux-scsi@vger.kernel.org;
v j <[EMAIL PROTECTED]> wrote:
> So far I have heard nothing but, "if you don't contribute, screw you."
That's exactly what you tell to the linux community: If they don't contribute
to your project *FOR*NOTHING*IN*RETURN*, you'll punish them by - stamping
your feet, crying out loud and *paying*
Jeff Garzik wrote:
--- a/include/linux/ata.h
+++ b/include/linux/ata.h
@@ -352,7 +352,7 @@ static inline int ata_drive_40wire(const u16 *dev_id)
{
if (ata_id_major_version(dev_id) >= 5 && ata_id_is_sata(dev_id))
return 0; /* SATA */
- if (dev_id[93] & 0x4000)
Pavel Machek wrote:
You know it is ugly. Alan demonstrated it even hurts performance, but
being ugly is the main problem.
No argument with that. Well, we're ok with dropping it. Actually,
reverting the entire set of udelay changes now seems wise. The same bug
that happened with i8042
On Thu, 15 Feb 2007 22:18:39 +
Ralf Baechle <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 15, 2007 at 01:53:58PM -0800, Andrew Morton wrote:
>
> > > The whole union thing was only needed to get rid of a warning but Marcel's
> > > solution does the same thing by attaching the packed keyword to the
On Thu, 15 Feb 2007 15:31:42 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Thu, 15 Feb 2007 22:30:17 +0100
> "J.A. Magall__n" <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 15 Feb 2007 05:14:08 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > Temporarily at
> > >
> > >
On Fri, 2007-02-16 at 00:24 +0100, Pavel Machek wrote:
> > The led framework is generic. If you can write a function to turn it
> > on/off you can drive it with the LED framework.
>
> Even if that function is slow and sleeps?
The LED class itself can call in interrupt context so you'd have to
The pile that was waiting for post-conference, largely bug fixes.
As mentioned in the last push, were two other push points planned for
2.6.21:
1) merge libata support for ACPI
2) Remove ugly combined mode hacks in libata-sff and pci/quirks, now
that old-IDE and libata have the necessary
> Maybe we should select CONFIG_PNP from CONFIG_ACPI?
That would be probably better I think because it will fix existing
user configurations. You'll get the defconfig for free with that too.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Thursday February 15, [EMAIL PROTECTED] wrote:
>
> With my ide driver and the md stuff all built into the kernel, my software
> raid drives and associated /dev/md? devices are detected and created by the
> kernel.
Yep.
>
> With the md stuff built in but the ide driver modular and loaded
>> If EIOCBRETRY then generic_file_aio_write() will be recalled for the
>> same iocb.
> Only if kick_iocb() is called. It won't be called if i_i_p2_r() was
> the only thing to return -EIOCBRETRY.
It is not need to call kick_iocb()
for generic_file_aio_write() calling.
It is recalled without any
linux-os (Dick Johnson) wrote:
There are a lot of device drivers that will never make it into the
mainline kernel because they are for one-of-a-kind devices or boards
that companies embed into their products. Nobody would even want a
copy of the software to interface with something that they
On Thu, 15 Feb 2007 22:30:17 +0100
"J.A. Magall__n" <[EMAIL PROTECTED]> wrote:
> On Thu, 15 Feb 2007 05:14:08 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.20-mm1/
> >
> > Will appear later at
> >
> >
> >
Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
>
> > >I do not know the LED subsystem in detail, but I do not
> > >know
> > >any possibility to access the i8042 from different
> > >subsystem
> > >than the input subsystem.
> > >
> > >What do you think and recommend?
> >
> > I think you need
On Thu, 2007-02-15 at 01:38 +0100, Nick Piggin wrote:
> On Wed, Feb 14, 2007 at 03:32:04PM -0500, Lee Schermerhorn wrote:
> > On Tue, 2007-02-13 at 07:09 +0100, Nick Piggin wrote:
> > > Hi,
> > >
> > > Just tinkering around with this and got something working, so I'll see
> > > if anyone else
On Thu, 15 Feb 2007 13:25:49 -0800
Randy Dunlap <[EMAIL PROTECTED]> wrote:
> From: Randy Dunlap <[EMAIL PROTECTED]>
>
> Are we ready to do this?
> I'd love for Tony to return, but he's been missing for awhile now.
>
> So this give us the following major areas that are marked as Orphan:
>
>
Hi!
> > > > >I do not know the LED subsystem in detail, but I do not
> > > > >know any possibility to access the i8042 from different
> > > > >subsystem than the input subsystem.
> > > > >
> > > > >What do you think and recommend?
> > > >
> > > > I think you need to use leds framework for what
Andrew Morton napisał(a):
> On Thu, 15 Feb 2007 15:37:20 +0100
> Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
>> Andrew Morton napisa__(a):
>>> Temporarily at
>>>
>>> http://userweb.kernel.org/~akpm/2.6.20-mm1/
>>>
>>> Will appear later at
>>>
>>>
>>>
On Thu, 2007-02-15 at 17:41 -0500, Jeff Garzik wrote:
> Bernd Petrovitsch wrote:
> > On Thu, 2007-02-15 at 18:40 +1100, Nick Piggin wrote:
> >> Rhetorical question: what stops me from taking somebody's copyrighted
> >> work, stripping the copyrights or falsely claiming to have a license
> >> to
Andrew Morton wrote:
On 15 Feb 2007 10:28:57 -0500
[EMAIL PROTECTED] (Frank Ch. Eigler) wrote:
akpm wrote:
[...] And what can I do with these markers? And once I've done it,
are there any userspace applications I can use to get the data out
in human-usable form? [...]
The
Mauro Carvalho Chehab wrote:
Basically, this series adds support for a bunch of newer cards and newer
drivers, do some relevant cleanups on cx88 (improving source code
readability and reducing binary code size), adds FM radio support on
pvrusb2 and do several other fixes and improvements.
On Thu, 2007-02-15 at 23:47 +0100, Németh Márton wrote:
> Pavel Machek <[EMAIL PROTECTED]> wrote:
> > > >I do not know the LED subsystem in detail, but I do not
> > > >know any possibility to access the i8042 from different
> > > >subsystem than the input subsystem.
> > > >
> > > >What do you
On Thu, 15 Feb 2007 22:26:10 + (GMT) James Simmons wrote:
>
> I wouldn't say it orphan. I just can't spend 8 hours a day on it.
> Alot of patches have been flowing into the layer.
So would you like to leave it as Maintained or change it to
"Odd Fixes"? (Maintained => a maintainer) From
Robert Hancock wrote:
ADMA-capable controllers provide a bit in the status register that appears
to indicate that the controller detected an SError condition. Update
sata_nv
to detect this and trigger error handling in order to handle the fault.
Signed-off-by: Robert Hancock <[EMAIL
Zhang, Yanmin wrote:
On Thu, 2007-02-08 at 20:19 -0500, Jeff Garzik wrote:
Zhang, Yanmin wrote:
If an ATA drive uses legacy mode, ata driver will choose 14 and 15 as the
fixed irq number. On ia64 platform, such numbers are GSI and should be converted
to irq vector.
Below patch against kernel
Koushik, Raju,
Please review, comment, and if you find this acceptable,
please forward upstream. This patch incorporates all of
fixes resulting from the last set of discussions, circa
November 2006.
--linas
This patch adds PCI error recovery support to the
s2io 10-Gigabit ethernet device
Hi!
> Apart from that I did the following changes:
> - implemented suspend/resume support (not tested very much)
> - named the registers
> - fixed a bug that caused a major slowdown when modprobed without debug=1
> - added writting support (disabled by default, modprobe with write=1)
> Before you
Ralf Baechle wrote:
> Gcc info page says:
>
> [...]
> `packed'
> The `packed' attribute specifies that a variable or structure field
> should have the smallest possible alignment--one byte for a
> variable, and one bit for a field, unless you specify a larger
> value with the
Hi Jörn,
On Thu, 15 Feb 2007, [utf-8] Jörn Engel wrote:
On Thu, 15 February 2007 19:38:14 +0100, Juan Piernas Canovas wrote:
The patch for 2.6.11 is not still stable enough to be released. Be patient
;-)
While I don't want to discourage you, this is about the point in
development where
Len Brown <[EMAIL PROTECTED]> writes:
> e1000 faults in 2.6.20-git, while 2.6.20 worked fine.
>
> System is a D875PBZ with LOM.
>
> clues?
I'm guessing this is an old bug found by the following bit of
debug coded added into since v2.6.20
+#ifdef CONFIG_DEBUG_SHIRQ
+ if (irqflags &
The current driver is not setting the dev
field in the private data structure, which
can lead to an OOPS if the driver tries to
report an error.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
--- linux-2.6.20/drivers/video/s3c2410fb.c 2007-02-04 18:44:54.0
+
+++
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Thu, 15 Feb 2007 17:01:27 +0100
> Tilman Schmidt <[EMAIL PROTECTED]> wrote:
>
> > Trying to build 2.6.20-mm1 on i386 with C=1, sparse 0.2 chokes
> > on arch/i386/kernel/i8253.c:
> >
> > CHECK arch/i386/kernel/i8253.c
> > linux/marker.h: No such
On Thursday 15 February 2007 14:14, Andrew Morton wrote:
> - The IDE tree got dropped due to various linkage problems
Doh, I guess this is what one gets for not testing modular
IDE driver support properly. :(
All linkage problems should be fixed now, sorry for that.
Bart
-
To unsubscribe from
101 - 200 of 1060 matches
Mail list logo
