public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dave Dillow <dave@thedillows.org>,
	Gene Heskett <gene.heskett@gmail.com>,
	linux-kernel@vger.kernel.org, ray-gmail@madrabbit.org,
	amanda-hackers@amanda.org, amanda-users@amanda.org
Subject: Re: plain 2.6.21-rc5 (1) vs amanda (0)
Date: Wed, 4 Apr 2007 10:42:19 -0700	[thread overview]
Message-ID: <20070404104219.40e25b6a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070404084530.GB1556@elte.hu>

On Wed, 4 Apr 2007 10:45:30 +0200 Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Dave Dillow <dave@thedillows.org> wrote:
> 
> > > Then it is a matter of figuring out why the device number changed -- 
> > > I'm thinking it is device-mapper, but will look closer tomorrow.
> > 
> > This commit is the one that changed it:
> > 
> > commit fdf892be32d84a1745fa0aee5fc60517421b8038
> > Author: Andrew Morton <akpm@osdl.org>
> > Date:   Mon Feb 12 00:51:44 2007 -0800
> > 
> >     [PATCH] register_blkdev(): don't hand out the LOCAL/EXPERIMENTAL majors
> >     
> >     As pointed out in http://bugzilla.kernel.org/show_bug.cgi?id=7922, 
> >     dynamic blockdev major allocation can hand out majors which LANANA 
> >     has defined as being for local/experimental use.
> 
> i dont think we should break backwards compatibility with a system that 
> has not changed any hardware. Andrew, should we revert this?

Well that's an odd thing for a backup program to be doing - there are any
number of things which could cause a dynamically-allocated major to change.

ho hum, yes, I guess it needs to go.

  reply	other threads:[~2007-04-04 17:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01  5:00 plain 2.6.21-rc5 (1) vs amanda (0) Gene Heskett
2007-04-01  6:51 ` Ingo Molnar
2007-04-01 14:44   ` Gene Heskett
2007-04-01  7:33 ` Ray Lee
2007-04-01 15:41   ` Gene Heskett
2007-04-02  4:20     ` Gene Heskett
2007-04-02  4:31       ` Dave Dillow
2007-04-04  4:34         ` Dave Dillow
2007-04-04  8:45           ` Ingo Molnar
2007-04-04 17:42             ` Andrew Morton [this message]
2007-04-04 18:17               ` Dave Dillow
2007-04-04 20:29                 ` Andrew Morton
2007-04-04 21:55                   ` Dave Dillow
2007-04-05  0:49                     ` Gene Heskett
2007-04-09 15:33           ` Gene Heskett
2007-04-09 15:59             ` Dave Dillow
2007-04-09 16:12               ` Gene Heskett
2007-04-09 16:30               ` Gene Heskett
2007-04-09 16:00             ` Ingo Molnar
2007-04-09 17:05               ` Gene Heskett
2007-04-09 17:50                 ` Ingo Molnar
2007-04-09 19:58                   ` Gene Heskett

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=20070404104219.40e25b6a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=amanda-hackers@amanda.org \
    --cc=amanda-users@amanda.org \
    --cc=dave@thedillows.org \
    --cc=gene.heskett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ray-gmail@madrabbit.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox