All of lore.kernel.org
 help / color / mirror / Atom feed
From: ashwinc@aftek.com
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: is this a bug ?
Date: Fri, 19 Aug 2005 14:31:50 -0500 (CDT)	[thread overview]
Message-ID: <9291.59.95.3.108.1124479910.squirrel@59.95.3.108> (raw)
In-Reply-To: <1124475944.23647.389.camel@tglx.tec.linutronix.de>


> So what ? You were asking a question about 2.4.19 and you got an answer
> related to that. It's coded that way in the ancient, broken and obsolete
> 2.4.19...

Couldnt agree more. But the deadlines prohibit us from upgrading it right
now. In fact I  have already fired up the board with 2.6.12-2 as stated
earlier, but theres still a while till I get everything we have running on
it.

>
> Where is the bug ?

Well, the fact that it works without any changes in 2.6.x, and that I had
to change it in 2.4. Basically, it seemed strange that rootflags is just
passed in from do_mount, remains unchanged, and later reassigned to
sb->flags in super.c.... seemed strange thats all. BTW I still need to
find out whats done differently in 2.6.x. I'm not implying this is a jffs2
bug anywhere, I just posted this to see if anyone else observed this,
since there are several others still using 2.4.19. Also, I didnt know of
the cmdline way of doing this without hacking into the source. Call me a
rookie if you want.

Well, now I know :)

Cheers,
Ashwin






**************************Disclaimer************************************
Information contained in this E-MAIL being proprietary to Aftek Infosys Limited 
is 'privileged' and 'confidential' and intended for use only by the individual
or entity to which it is addressed. You are notified that any use, copying 
or dissemination of the information contained in the E-MAIL in any manner 
whatsoever is strictly prohibited.
***************************************************************************
http://www.aftek.com/

  reply	other threads:[~2005-08-19 19:20 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20  0:14 is this a bug ? Ashwin Chaugule
2005-08-19 13:19 ` Thomas Gleixner
2005-08-20  1:36   ` Ashwin Chaugule
2005-08-19 18:25     ` Thomas Gleixner
2005-08-19 19:31       ` ashwinc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-21  3:08 Is this a bug? Peter Teoh
2013-02-19  9:32 David Wade
2013-02-19  9:42 ` Andreas Ericsson
2013-02-19  9:47 ` Erik Faye-Lund
2013-02-19 11:02   ` Duy Nguyen
2013-02-22 19:29     ` Phil Hord
2013-02-22 21:48       ` Junio C Hamano
2011-06-21 21:57 Is this a Bug? Christian Deussen
2011-06-21 22:49 ` Greg Freemyer
2011-06-22  7:28   ` Wilson Felipe
2011-06-22 19:50     ` julie Sullivan
2011-06-22 21:21       ` julie Sullivan
2011-06-23 12:16         ` Christian D.
2011-06-23 13:03           ` Jonathan Neuschäfer
2011-06-23 18:49 ` Jonathan Neuschäfer
2011-04-02  8:05 Is this a bug? Ding Dinghua
2011-04-02 16:32 ` Amir Goldstein
2011-04-03  9:24   ` Ding Dinghua
2011-04-03 14:51     ` Yongqiang Yang
2011-04-03 15:44       ` Amir Goldstein
2011-03-24  0:46 is " Jay
2011-03-25 15:18 ` Steven Rostedt
2002-07-15 13:57 Is " Tisserand Patrice
2002-07-15 14:08 ` Takashi Iwai
2001-08-07 11:51 is " Thodoris Pitikaris
2001-08-07 13:51 ` Andrzej Krzysztofowicz
2001-08-08  2:19 ` Dr. Kelsey Hudson
2001-08-08  3:15   ` J Sloan
2001-08-08  3:45     ` Dr. Kelsey Hudson
2001-08-08 10:53       ` David Weinehall
2001-08-08 11:05   ` Alan Cox
2001-08-08 12:59   ` Ron Flory
2001-08-08 16:51 ` jury gerold
2001-08-10  9:12   ` Eric W. Biederman
2001-08-10 12:22     ` jury gerold
2001-08-10 16:22       ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9291.59.95.3.108.1124479910.squirrel@59.95.3.108 \
    --to=ashwinc@aftek.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.