The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, dhowells@redhat.com
Subject: Re: [PATCH 0 of 11] Use SEEK_{SET,CUR,END} instead of hardcoded values
Date: Mon, 18 Sep 2006 11:32:36 +0100	[thread overview]
Message-ID: <2504.1158575556@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <patchbomb.1158455366@turing.ams.sunysb.edu>

Josef 'Jeff' Sipek <jeffpc@josefsipek.net> wrote:

> In July, David Howells added SEEK_{SET,CUR,END} definitions to
> include/linux/fs.h
> 
> The following patches convert offenders which were found by grep'ing the
> source tree.

Looks good, though I think you do have to drop the XFS portion of the patch,
though you could strip the comments from the case statements there.

So NAK for the XFS patch, but for the rest:

Acked-By: David Howells <dhowells@redhat.com>

      parent reply	other threads:[~2006-09-18 10:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17  1:09 [PATCH 0 of 11] Use SEEK_{SET,CUR,END} instead of hardcoded values Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 1 of 11] MBCS: Use SEEK_{SET, CUR, END} " Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 2 of 11] EICON ISDN: Removed unused definitions for OS_SEEK_* Josef 'Jeff' Sipek
2006-09-17  8:48   ` Armin Schindler
2006-09-17  1:09 ` [PATCH 3 of 11] MTD: Use SEEK_{SET, CUR, END} instead of hardcoded values Josef 'Jeff' Sipek
2006-09-17 16:06   ` David Woodhouse
2006-09-17  1:09 ` [PATCH 4 of 11] CIFS: Use SEEK_END instead of hardcoded value Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 5 of 11] XFS: Use SEEK_{SET, CUR, END} instead of hardcoded values Josef 'Jeff' Sipek
2006-09-18  3:34   ` David Chinner
2006-09-18 10:30     ` David Howells
2006-09-19  4:01       ` David Chinner
2006-09-17  1:09 ` [PATCH 6 of 11] NFS: Use SEEK_END instead of hardcoded value Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 7 of 11] VFS: Use SEEK_{SET, CUR, END} instead of hardcoded values Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 8 of 11] sound core: " Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 9 of 11] opl4: " Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 10 of 11] gus: " Josef 'Jeff' Sipek
2006-09-17  1:09 ` [PATCH 11 of 11] mixart: " Josef 'Jeff' Sipek
2006-09-17  3:46 ` [PATCH 0 of 11] Use SEEK_{SET,CUR,END} " Nick Piggin
2006-09-17  6:38   ` Josef Sipek
2006-09-18 10:32 ` David Howells [this message]

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=2504.1158575556@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=jeffpc@josefsipek.net \
    --cc=linux-kernel@vger.kernel.org \
    /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