On Wed, Dec 13, 2006 at 02:05:59PM +0100, Adrian Bunk wrote:
> <-- snip -->
>
> ...
> NOT FOR MAINLINE!
>
> This is for the driver tutorial I give. It will not be included in the
> mainline kernel tree ever. Use the ldusb driver that is already there
> instead for this device.
>
> This is
On Wed, Dec 13, 2006 at 02:05:59PM +0100, Adrian Bunk wrote:
-- snip --
...
NOT FOR MAINLINE!
This is for the driver tutorial I give. It will not be included in the
mainline kernel tree ever. Use the ldusb driver that is already there
instead for this device.
This is only a
On Mon, 2006-12-11 at 17:42 +0100, Adrian Bunk wrote:
> The MTD_UBI and the MTD_UBI_DEBUG_PARANOID_* options lack help texts.
thanks, fixed in our GIT tree.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Mon, 2006-12-11 at 21:46 +0100, Adrian Bunk wrote:
> It doesn't seem to be intended that in ubi_dbg_vprint_nolock() the
> variable "caller" is never assigned any value different from 0.
>
thanks, fixed in our GIT tree.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
-
To unsubscribe
On Wednesday, 13 December 2006 01:53, Neil Brown wrote:
> On Tuesday December 12, [EMAIL PROTECTED] wrote:
> > >
> > > So when md writes to write out the superblock, to gets EIO... Odd that
> > > you aren't getting errors for normal writes.
> > >
> > > What devices are the md/raid1 built on?
> >
On Wednesday, 13 December 2006 01:53, Neil Brown wrote:
On Tuesday December 12, [EMAIL PROTECTED] wrote:
So when md writes to write out the superblock, to gets EIO... Odd that
you aren't getting errors for normal writes.
What devices are the md/raid1 built on?
Sata drives,
On Mon, 2006-12-11 at 21:46 +0100, Adrian Bunk wrote:
It doesn't seem to be intended that in ubi_dbg_vprint_nolock() the
variable caller is never assigned any value different from 0.
thanks, fixed in our GIT tree.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
-
To unsubscribe from
On Mon, 2006-12-11 at 17:42 +0100, Adrian Bunk wrote:
The MTD_UBI and the MTD_UBI_DEBUG_PARANOID_* options lack help texts.
thanks, fixed in our GIT tree.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
On Wed, 13 Dec 2006 09:17:42 +0800
Conke Hu <[EMAIL PROTECTED]> wrote:
> Thank you for applying ATI SB600 SATA patch!
> But it seems the patch file name should be
> "ati"-sb600-sata-quirk.patch, not "via"-sb600-sata-quirk.patch, type
> error? :)
That's the sort of thing which happens
On Tuesday December 12, [EMAIL PROTECTED] wrote:
> >
> > So when md writes to write out the superblock, to gets EIO... Odd that
> > you aren't getting errors for normal writes.
> >
> > What devices are the md/raid1 built on?
>
> Sata drives, on sata_uli.
>
> > >
> > > I'll try to reproduce it
On Tuesday, 12 December 2006 00:54, Neil Brown wrote:
> On Tuesday December 12, [EMAIL PROTECTED] wrote:
> > On Monday, 11 December 2006 23:52, Neil Brown wrote:
> > > On Monday December 11, [EMAIL PROTECTED] wrote:
> > > > Hi,
> > > >
> > > > On Monday, 11 December 2006 09:58, Andrew Morton
On 12/11/06, Adrian Bunk <[EMAIL PROTECTED]> wrote:
On Mon, Dec 11, 2006 at 12:58:07AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.19-rc6-mm2:
>...
> git-ubi.patch
>...
> git trees.
>...
It doesn't seem to be intended that in ubi_dbg_vprint_nolock() the
variable "caller" is never
On Tue, 12 Dec 2006 15:43:54 +0900
KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> On Mon, 11 Dec 2006 22:06:17 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
> > > When I use ftp on 2.6.19-mm1, transfered file is always broken.
> > > like this:
> > > ==
> > > [EMAIL PROTECTED] ~]$ file
On Tue, 12 Dec 2006 15:43:54 +0900
KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote:
On Mon, 11 Dec 2006 22:06:17 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
When I use ftp on 2.6.19-mm1, transfered file is always broken.
like this:
==
[EMAIL PROTECTED] ~]$ file ./linux-2.6.19.tar.bz2
On 12/11/06, Adrian Bunk [EMAIL PROTECTED] wrote:
On Mon, Dec 11, 2006 at 12:58:07AM -0800, Andrew Morton wrote:
...
Changes since 2.6.19-rc6-mm2:
...
git-ubi.patch
...
git trees.
...
It doesn't seem to be intended that in ubi_dbg_vprint_nolock() the
variable caller is never assigned any
On Tuesday, 12 December 2006 00:54, Neil Brown wrote:
On Tuesday December 12, [EMAIL PROTECTED] wrote:
On Monday, 11 December 2006 23:52, Neil Brown wrote:
On Monday December 11, [EMAIL PROTECTED] wrote:
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
On Tuesday December 12, [EMAIL PROTECTED] wrote:
So when md writes to write out the superblock, to gets EIO... Odd that
you aren't getting errors for normal writes.
What devices are the md/raid1 built on?
Sata drives, on sata_uli.
I'll try to reproduce it tomorrow and
On Wed, 13 Dec 2006 09:17:42 +0800
Conke Hu [EMAIL PROTECTED] wrote:
Thank you for applying ATI SB600 SATA patch!
But it seems the patch file name should be
ati-sb600-sata-quirk.patch, not via-sb600-sata-quirk.patch, type
error? :)
That's the sort of thing which happens when people
On Mon, 11 Dec 2006 22:06:17 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> > When I use ftp on 2.6.19-mm1, transfered file is always broken.
> > like this:
> > ==
> > [EMAIL PROTECTED] ~]$ file ./linux-2.6.19.tar.bz2 (got on 2.6.19-mm1)
> > ./linux-2.6.19.tar.bz2: data
> > (I confirmed original
On Tue, 12 Dec 2006 14:53:41 +0900
KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
>
> On Mon, 11 Dec 2006 00:58:07 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.19-mm1/
> >
> > Will appear later at
> >
> >
> >
On Mon, 11 Dec 2006 00:58:07 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.19-mm1/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
>
When I use ftp on
On Tuesday December 12, [EMAIL PROTECTED] wrote:
> On Monday, 11 December 2006 23:52, Neil Brown wrote:
> > On Monday December 11, [EMAIL PROTECTED] wrote:
> > > Hi,
> > >
> > > On Monday, 11 December 2006 09:58, Andrew Morton wrote:
> > > >
> > > > Temporarily at
> > > >
> > > >
On Monday, 11 December 2006 23:52, Neil Brown wrote:
> On Monday December 11, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > On Monday, 11 December 2006 09:58, Andrew Morton wrote:
> > >
> > > Temporarily at
> > >
> > > http://userweb.kernel.org/~akpm/2.6.19-mm1/
> > >
> > > Will appear later at
>
On Monday December 11, [EMAIL PROTECTED] wrote:
> Hi,
>
> On Monday, 11 December 2006 09:58, Andrew Morton wrote:
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.19-mm1/
> >
> > Will appear later at
> >
> >
> >
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.19-mm1/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
It caused all of the md RAID1s on my
On Tue, 12 Dec 2006, Nick Piggin wrote:
> > >Do you have CONFIG_DEBUG_VM turned on? I think we miss clearning
> > >BH_New in some places, thus causing an error path to zero the block
> > >incorrectly if we hit an error that CONFIG_DEBUG_VM makes much more
> > >likely.
> > Yes, I have. Will
Jiri Kosina wrote:
On Tue, 12 Dec 2006, Nick Piggin wrote:
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run.
It looks like this, after dhclient finishes:
Do you have CONFIG_DEBUG_VM turned on? I think
On Tue, 12 Dec 2006, Nick Piggin wrote:
> > Am I the only one seeing something strange on ext3 with this kernel?
> > For example /etc/resolv.conf gets corrupted during the dhclient run.
> > It looks like this, after dhclient finishes:
> Do you have CONFIG_DEBUG_VM turned on? I think we miss
Jiri Kosina wrote:
On Mon, 11 Dec 2006, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run. It
looks like this,
On Mon, 11 Dec 2006, Andrew Morton wrote:
> Temporarily at
> http://userweb.kernel.org/~akpm/2.6.19-mm1/
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run. It
looks like this, after dhclient finishes:
Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
- There's some new runtime debugging in kmap_atomic(). It catches one
buglet in in
Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
- There's some new runtime debugging in kmap_atomic(). It catches one
buglet in in
On Mon, 11 Dec 2006, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run. It
looks like this, after dhclient finishes:
Jiri Kosina wrote:
On Mon, 11 Dec 2006, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run. It
looks like this,
On Tue, 12 Dec 2006, Nick Piggin wrote:
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run.
It looks like this, after dhclient finishes:
Do you have CONFIG_DEBUG_VM turned on? I think we miss clearning
Jiri Kosina wrote:
On Tue, 12 Dec 2006, Nick Piggin wrote:
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run.
It looks like this, after dhclient finishes:
Do you have CONFIG_DEBUG_VM turned on? I think
On Tue, 12 Dec 2006, Nick Piggin wrote:
Do you have CONFIG_DEBUG_VM turned on? I think we miss clearning
BH_New in some places, thus causing an error path to zero the block
incorrectly if we hit an error that CONFIG_DEBUG_VM makes much more
likely.
Yes, I have. Will retry without it
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
It caused all of the md RAID1s on my test box to
On Monday December 11, [EMAIL PROTECTED] wrote:
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
On Monday, 11 December 2006 23:52, Neil Brown wrote:
On Monday December 11, [EMAIL PROTECTED] wrote:
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
On Tuesday December 12, [EMAIL PROTECTED] wrote:
On Monday, 11 December 2006 23:52, Neil Brown wrote:
On Monday December 11, [EMAIL PROTECTED] wrote:
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
On Mon, 11 Dec 2006 00:58:07 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
When I use ftp on 2.6.19-mm1,
On Tue, 12 Dec 2006 14:53:41 +0900
KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote:
On Mon, 11 Dec 2006 00:58:07 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
On Mon, 11 Dec 2006 22:06:17 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
When I use ftp on 2.6.19-mm1, transfered file is always broken.
like this:
==
[EMAIL PROTECTED] ~]$ file ./linux-2.6.19.tar.bz2 (got on 2.6.19-mm1)
./linux-2.6.19.tar.bz2: data
(I confirmed original file was not
44 matches
Mail list logo