public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: sct@redhat.com (Stephen C. Tweedie)
Cc: alan@redhat.com (Alan Cox), sct@redhat.com (Stephen Tweedie),
	linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: O_DIRECT
Date: Fri, 27 Jun 2003 07:07:02 -0400 (EDT)	[thread overview]
Message-ID: <200306271107.h5RB72x32196@devserv.devel.redhat.com> (raw)
In-Reply-To: <1056710121.2418.19.camel@sisko.scot.redhat.com> from "Stephen C. Tweedie" at Meh 27, 2003 11:35:21

> Ouch ouch ouch, there's nasty merge conflict between the O_DIRECT patch
> and an existing 64-bit rlimit chunk in -ac3.  You really, really want
> the change below. :-)  Marcelo's tree appears OK, and this is a common
> code path for all filesystems in -ac, so it matches the failure patterns
> that far.

Ouch indeed - ok thats good, that means its not the O_DIRECT stuff. Thanks
for figuring it out

  reply	other threads:[~2003-06-27 10:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200306262021.h5QKLhN10771@devserv.devel.redhat.com>
     [not found] ` <1056706819.2418.11.camel@sisko.scot.redhat.com>
2003-06-27 10:35   ` O_DIRECT Stephen C. Tweedie
2003-06-27 11:07     ` Alan Cox [this message]
2004-07-20 17:27 O_DIRECT Shesha Sreenivasamurthy
2004-07-20 18:48 ` O_DIRECT bert hubert
     [not found]   ` <40FD6FCB.5020408@inostor.com>
2004-07-20 20:17     ` O_DIRECT bert hubert
2004-07-21  0:10   ` O_DIRECT Rob van Nieuwkerk
2004-07-21 14:45   ` O_DIRECT Devel
     [not found]     ` <40FE9F3F.2090205@inostor.com>
2004-07-22  9:46       ` O_DIRECT Devel
2004-07-24  9:56   ` O_DIRECT Rogier Wolff
2004-07-26  1:24     ` O_DIRECT Andrew Morton
2004-07-21  0:05 ` O_DIRECT Rob van Nieuwkerk
     [not found]   ` <40FEA382.8050700@inostor.com>
2004-07-21 17:20     ` O_DIRECT Rob van Nieuwkerk
     [not found]       ` <40FEAF70.4070407@inostor.com>
2004-07-21 18:15         ` O_DIRECT Rob van Nieuwkerk
2004-07-21 18:45           ` O_DIRECT Shesha Sreenivasamurthy
2004-07-21 23:18           ` O_DIRECT Shesha Sreenivasamurthy
2004-07-21 23:54             ` O_DIRECT Rob van Nieuwkerk
2004-07-22  0:00               ` O_DIRECT Shesha Sreenivasamurthy
2004-07-22  0:18                 ` O_DIRECT Rob van Nieuwkerk
2004-07-22  0:48                   ` O_DIRECT Shesha Sreenivasamurthy
     [not found] <200208291113.g7TBDut26852@tench.street-vision.com>
2002-08-29 11:22 ` O_DIRECT Peter T. Breuer
2002-08-29 12:14 ` O_DIRECT Peter T. Breuer
  -- strict thread matches above, loose matches on Subject: below --
2002-08-29 11:04 O_DIRECT Peter T. Breuer
2001-04-12 21:09 O_DIRECT Andrea Arcangeli

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=200306271107.h5RB72x32196@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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