Bug 11225 - mtdsuper.c BLOCK=n compile error
Summary: mtdsuper.c BLOCK=n compile error
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Flash/Memory Technology Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: David Woodhouse
URL:
Keywords:
Depends on:
Blocks: Regressions-2.6.26
  Show dependency tree
 
Reported: 2008-08-01 15:33 UTC by Adrian Bunk
Modified: 2008-08-04 11:05 UTC (History)
0 users

See Also:
Kernel Version: 2.6.27-rc1-git
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description Adrian Bunk 2008-08-01 15:33:36 UTC
Subject         : mtdsuper.c BLOCK=n compile error
Submitter       : Adrian Bunk <bunk@kernel.org>
References      : http://lkml.org/lkml/2008/8/1/454
Comment 1 Adrian Bunk 2008-08-02 04:24:16 UTC
Handled-By      : David Woodhouse <dwmw2@infradead.org>
Patch           : http://lkml.org/lkml/2008/8/1/499
Comment 2 Rafael J. Wysocki 2008-08-02 13:09:24 UTC
On Saturday, 2 of August 2008, Adrian Bunk wrote:
> On Sat, Aug 02, 2008 at 08:04:20PM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.26.  Please verify if it still should be listed
> > and let me know (either way).
> 
> yes
> 
> > Bug-Entry   : http://bugzilla.kernel.org/show_bug.cgi?id=11225
> > Subject             : mtdsuper.c BLOCK=n compile error
> > Submitter   : Adrian Bunk <bunk@kernel.org>
> > Date                : 2008-08-01 15:33 (2 days old)
> > References  : http://lkml.org/lkml/2008/8/1/454
> > Handled-By  : David Woodhouse <dwmw2@infradead.org>
> > Patch               : http://lkml.org/lkml/2008/8/1/499
Comment 3 David Woodhouse 2008-08-02 13:53:45 UTC
The fix for this is in git://git.infradead.org/users/dwmw2/random-2.6.git and Linus has been asked to pull it. Thanks.
Comment 4 Adrian Bunk 2008-08-04 11:05:16 UTC
fixed by commit f1136d022af8f07a97f59c6d07483bdb82ffbd8e

Note You need to log in before you can comment on or make changes to this bug.