All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: ide tree build failure
Date: Tue, 26 Aug 2008 22:04:04 +0200	[thread overview]
Message-ID: <200808262204.05075.bzolnier@gmail.com> (raw)
In-Reply-To: <20080826140658.316d9727.sfr@canb.auug.org.au>


Hi,

On Tuesday 26 August 2008, Stephen Rothwell wrote:
> Hi Bart,
> 
> Today's linux-next build (x86_64_allmodconfig) failed like this:
> 
> ERROR: "ide_floppy_ioctl" [drivers/ide/ide-floppy_mod.ko] undefined!
> 
> Introduced by commit 487a606ecd39be80655bddc7f8d14bfdf48bf682
> ("ide-floppy: move all ioctl handling to ide-floppy_ioctl.c").
> 
> I added the following patch.

I integrated it into the guilty commit, thanks!

  reply	other threads:[~2008-08-26 20:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26  4:06 linux-next: ide tree build failure Stephen Rothwell
2008-08-26 20:04 ` Bartlomiej Zolnierkiewicz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-15  1:34 Stephen Rothwell
2009-06-15  5:35 ` Borislav Petkov
2009-06-15 16:14   ` Bartlomiej Zolnierkiewicz
2009-02-06  3:35 Stephen Rothwell
2009-01-22  1:57 Stephen Rothwell
2009-01-22 13:22 ` Bartlomiej Zolnierkiewicz
2009-01-22 22:14   ` Stephen Rothwell
2008-12-08  2:16 Stephen Rothwell
2008-12-08 17:10 ` Bartlomiej Zolnierkiewicz
2008-12-08 17:49   ` Borislav Petkov
2008-12-09  0:12   ` Stephen Rothwell
2008-08-12  1:18 Stephen Rothwell
2008-08-12  7:36 ` Borislav Petkov
2008-08-12  9:15   ` Bartlomiej Zolnierkiewicz
2008-07-24  3:17 Stephen Rothwell
2008-07-24 18:41 ` Bartlomiej Zolnierkiewicz
2008-06-30  5:28 Stephen Rothwell
2008-06-30 18:38 ` Bartlomiej Zolnierkiewicz
2008-07-01  0:28   ` Stephen Rothwell

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=200808262204.05075.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.