All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: orenl@cs.columbia.edu, xemul@parallels.com,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, hch@infradead.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	mingo@elte.hu
Subject: Re: C/R review
Date: Wed, 18 Mar 2009 10:53:34 -0700	[thread overview]
Message-ID: <1237398814.8286.174.camel@nimitz> (raw)
In-Reply-To: <20090317210110.GA3897@x200.localdomain>

On Wed, 2009-03-18 at 00:01 +0300, Alexey Dobriyan wrote:
> > +static inline loff_t file_pos_read(struct file *file)
> > +{
> > +     return file->f_pos;
> > +}
> > +
> > +static inline void file_pos_write(struct file *file, loff_t pos)
> > +{
> > +     file->f_pos = pos;
> > +}
> 
> I failed myself to understand need for this wrappers at all.
> 
> If dump is single-threaded, who is going to change f_pos under you?
> 
> I'm passing &file->f_pos to vfs_write().

/me git-blames...

They're already in the kernel and they've been there since the beginning
of git as far as I can see.  I think Oren was just trying to use what is
there already, so he moved them to a header.

-- Dave


  parent reply	other threads:[~2009-03-18 17:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 21:01 C/R review Alexey Dobriyan
2009-03-18  0:47 ` Serge E. Hallyn
2009-03-18  9:44   ` Oren Laadan
2009-03-18 10:19 ` Oren Laadan
2009-03-18 16:00   ` Dave Hansen
     [not found]   ` <49C0CAB9.3080500-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-03-18 16:00     ` Dave Hansen
     [not found] ` <20090317210110.GA3897-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
2009-03-18 10:19   ` Oren Laadan
2009-03-18 17:53   ` Dave Hansen
2009-03-18 17:53 ` Dave Hansen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-17 21:01 Alexey Dobriyan

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=1237398814.8286.174.camel@nimitz \
    --to=dave@linux.vnet.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=orenl@cs.columbia.edu \
    --cc=torvalds@linux-foundation.org \
    --cc=xemul@parallels.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 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.