From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>
Cc: linux-next@vger•kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@gmail•com>
Subject: Re: linux-next: manual merge of the bdev tree
Date: Fri, 17 Oct 2008 18:42:59 +1100 [thread overview]
Message-ID: <20081017184259.b66089bc.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081017183557.f831ab54.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
Hi Al,
On Fri, 17 Oct 2008 18:35:57 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the bdev tree got a conflict in
> drivers/ide/ide-floppy.c between commits from the ide tree and commit
> a55897a7d06734d1ae32124a5e19cb903c33b8e3 ("[PATCH] eliminate use of
> ->f_flags in block methods") from the bdev tree.
>
> Again you don't need to patch drivers/ide/ide-floppy.c any more, but
> drivers/ide/ide-gd.c instead. Patch below.
I got a bit harder after that ... so I have again dropped the bdev for
today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-17 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 7:35 linux-next: manual merge of the bdev tree Stephen Rothwell
2008-10-17 7:42 ` Stephen Rothwell [this message]
2008-10-17 8:58 ` Bartlomiej Zolnierkiewicz
2008-10-17 11:14 ` Al Viro
2008-10-17 13:24 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2008-10-17 7:29 Stephen Rothwell
2008-10-16 8:48 Stephen Rothwell
2008-09-18 6:23 Stephen Rothwell
2008-09-18 6:11 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=20081017184259.b66089bc.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bzolnier@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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