All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: Ming Lei <ming.lei@canonical.com>,
	Dmitry Kasatkin <d.kasatkin@samsung.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] firmware: read firmware size using i_size_read()
Date: Tue, 8 Jul 2014 15:26:24 -0700	[thread overview]
Message-ID: <20140708222624.GB7745@kroah.com> (raw)
In-Reply-To: <CACE9dm9bSLTMuaobgZNF+Xe7GxZZKjqedK91PsTjYrJWafMGiw@mail.gmail.com>

On Wed, Jun 25, 2014 at 07:46:41PM +0300, Dmitry Kasatkin wrote:
> On 13 June 2014 19:06, Dmitry Kasatkin <dmitry.kasatkin@gmail.com> wrote:
> > On 13 June 2014 19:03, Ming Lei <ming.lei@canonical.com> wrote:
> >> On Fri, Jun 13, 2014 at 11:09 PM, Dmitry Kasatkin
> >> <d.kasatkin@samsung.com> wrote:
> >>> There is no need to read attr because inode structure contains size
> >>> of the file. Use i_size_read() instead.
> >>>
> >>> Signed-off-by: Dmitry Kasatkin <d.kasatkin@samsung.com>
> >>
> >> Acked-by: Ming Lei <ming.lei@canonical.com>
> >>
> 
> 
> Hi,
> 
> BTW. To what tree it is applied?

Mine now, you should get an email soon...

      parent reply	other threads:[~2014-07-08 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 21:05 [PATCH 1/1] firmware: read firmware size using i_size_read() Dmitry Kasatkin
2014-06-13 14:56 ` Ming Lei
2014-06-13 15:09   ` [PATCH v2 0/1] " Dmitry Kasatkin
2014-06-13 15:09     ` [PATCH v2 1/1] firmware: " Dmitry Kasatkin
2014-06-13 16:03       ` Ming Lei
2014-06-13 16:06         ` Dmitry Kasatkin
2014-06-25 16:46           ` Dmitry Kasatkin
2014-07-02  1:33             ` Ming Lei
2014-07-02  5:27               ` Greg Kroah-Hartman
2014-07-08 22:26             ` Greg Kroah-Hartman [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=20140708222624.GB7745@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=d.kasatkin@samsung.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.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.