All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	linux-kernel@vger.kernel.org, Hansjoerg Lipp <hjlipp@web.de>
Subject: Re: mm snapshot broken-out-2007-01-26-00-36.tar.gz uploaded
Date: Sat, 27 Jan 2007 13:41:16 -0800	[thread overview]
Message-ID: <20070127134116.06bdadd8.akpm@osdl.org> (raw)
In-Reply-To: <45BBC444.8090109@imap.cc>

On Sat, 27 Jan 2007 22:29:40 +0100
Tilman Schmidt <tilman@imap.cc> wrote:

> Am 27.01.2007 17:37 schrieb Michal Piotrowski:
> > On 26/01/07, akpm@osdl.org <akpm@osdl.org> wrote:
> >> The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded to
> >>
> >>    ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-01-26-00-36.tar.gz
> >>
> > 
> > It's probably not mm snapshot related. This driver is just broken.
> 
> It probably *is* mm snapshot related. This driver compiles and works
> just fine in 2.6.19.2, 2.6.20-rc6 and 2.6.20-rc4-mm1.
> 
> > drivers/isdn/gigaset/bas-gigaset.c: In function 'dump_urb':
> > drivers/isdn/gigaset/bas-gigaset.c:258: error: 'struct urb' has no
> > member named 'bandwidth'
> 
> In current stable and mm releases, 'struct urb' *does* have a member
> named 'bandwidth'. If some mm patch removes that member then it is
> the responsibility of that patch to adapt all users of that structure
> accordingly.
> 

yup, there's a patch in Greg's USB tree which removes the bandwidth field. 
Mostly.  I fixed it up.

I have everything compiling now, mostly.  The number of fixes which were
needed was just extraordinary.  I'm thinking about making changes...

  reply	other threads:[~2007-01-27 21:41 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26  8:37 mm snapshot broken-out-2007-01-26-00-36.tar.gz uploaded akpm
2007-01-26 15:04 ` Michal Piotrowski
2007-01-26 15:33   ` Serge E. Hallyn
2007-01-26 15:38     ` Serge E. Hallyn
2007-01-26 16:06       ` Michal Piotrowski
2007-01-26 16:37 ` Michal Piotrowski
2007-01-26 16:46 ` Michal Piotrowski
2007-01-26 16:57 ` Michal Piotrowski
2007-01-26 17:29 ` Michal Piotrowski
2007-01-26 18:14   ` Serge E. Hallyn
2007-01-26 18:22     ` Michal Piotrowski
2007-01-26 18:58       ` Serge E. Hallyn
2007-01-26 17:48 ` Michal Piotrowski
2007-01-26 18:04 ` Michal Piotrowski
     [not found]   ` <6bffcb0e0701261008u2fd5a7d9va16d7fd9f250e14b@mail.gmail.com>
2007-01-26 18:38     ` Christoph Lameter
2007-01-26 18:43       ` Pavel Machek
2007-01-26 18:45       ` Michal Piotrowski
2007-01-26 19:07         ` Christoph Lameter
2007-01-26 19:20           ` Michal Piotrowski
2007-01-26 19:45 ` Michal Piotrowski
     [not found]   ` <6bffcb0e0701261523j3a84a357lad93260b5865c99d@mail.gmail.com>
2007-01-27  0:33     ` Andrew Morton
2007-01-27  0:41       ` Michal Piotrowski
2007-01-27  0:29 ` Michal Piotrowski
2007-01-27 15:05 ` Michal Piotrowski
2007-01-27 20:38   ` Herbert Xu
2007-01-27 16:03 ` Michal Piotrowski
2007-01-30  1:05   ` Tejun Heo
2007-01-27 16:14 ` Michal Piotrowski
2007-01-27 17:20 ` Michal Piotrowski
     [not found] ` <6bffcb0e0701270837i1ec40560l6e61e8876177e9da@mail.gmail.com>
2007-01-27 21:29   ` Tilman Schmidt
2007-01-27 21:41     ` Andrew Morton [this message]
2007-01-27 22:12       ` Michal Piotrowski
2007-01-27 23:25       ` Tilman Schmidt
2007-01-27 23:27         ` Michal Piotrowski
2007-01-28  2:41       ` Valdis.Kletnieks
2007-01-28  3:37         ` Michal Piotrowski
2007-01-29  2:49         ` Valdis.Kletnieks
2007-01-29  6:08           ` Eric W. Biederman
2007-01-29  6:45             ` Valdis.Kletnieks
2007-01-29  8:24               ` Eric W. Biederman
2007-01-29  2:58         ` Valdis.Kletnieks
2007-01-29  5:14           ` Randy Dunlap
2007-01-29  5:46           ` Valdis.Kletnieks

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=20070127134116.06bdadd8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hjlipp@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=tilman@imap.cc \
    /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.