From: 'Matt Fleming' <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: "Kweh,
Hock Leong"
<hock.leong.kweh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
"Ong,
Boon Leong"
<boon.leong.ong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Sam Protsenko
<semen.protsenko-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>,
Roy Franz <roy.franz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>,
James Bottomley
<James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>,
Linux FS Devel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Fleming,
Matt" <matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v5 2/2] efi: a misc char interface for user to update efi firmware
Date: Wed, 9 Sep 2015 15:04:48 +0100 [thread overview]
Message-ID: <20150909140448.GI4973@codeblueprint.co.uk> (raw)
In-Reply-To: <F54AEECA5E2B9541821D670476DAE19C4A85551A-j2khPEwRog0FyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Wed, 02 Sep, at 06:31:36AM, Kweh Hock Leong wrote:
>
> I have done an experiment on that by using the misc char device file note.
> I included the flush() callback function to the fops. In flush(), I put a printk()
> and return -EINVAL. When I perform "cat XXX > /dev/XXX" on Intel Quark
> Galileo platform, I found that the flush() is not just being called at file
> close, it will also being called before the file write. And the error return, that I
> forced in the flush(), does not show up at shell terminal. This is the reason that
> I did not follow James recommendation and figure out to do it at write().
OK, that's interesting. Which cat tool is included with the Quark BSP?
--
Matt Fleming, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: "'Matt Fleming'" <matt@codeblueprint.co.uk>
To: "Kweh, Hock Leong" <hock.leong.kweh@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Sam Protsenko <semen.protsenko@linaro.org>,
Peter Jones <pjones@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Roy Franz <roy.franz@linaro.org>, Borislav Petkov <bp@alien8.de>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"Fleming, Matt" <matt.fleming@intel.com>
Subject: Re: [PATCH v5 2/2] efi: a misc char interface for user to update efi firmware
Date: Wed, 9 Sep 2015 15:04:48 +0100 [thread overview]
Message-ID: <20150909140448.GI4973@codeblueprint.co.uk> (raw)
In-Reply-To: <F54AEECA5E2B9541821D670476DAE19C4A85551A@PGSMSX102.gar.corp.intel.com>
On Wed, 02 Sep, at 06:31:36AM, Kweh Hock Leong wrote:
>
> I have done an experiment on that by using the misc char device file note.
> I included the flush() callback function to the fops. In flush(), I put a printk()
> and return -EINVAL. When I perform "cat XXX > /dev/XXX" on Intel Quark
> Galileo platform, I found that the flush() is not just being called at file
> close, it will also being called before the file write. And the error return, that I
> forced in the flush(), does not show up at shell terminal. This is the reason that
> I did not follow James recommendation and figure out to do it at write().
OK, that's interesting. Which cat tool is included with the Quark BSP?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-09-09 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 6:31 [PATCH v5 2/2] efi: a misc char interface for user to update efi firmware Kweh, Hock Leong
[not found] ` <F54AEECA5E2B9541821D670476DAE19C4A85551A-j2khPEwRog0FyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-09-09 14:04 ` 'Matt Fleming' [this message]
2015-09-09 14:04 ` 'Matt Fleming'
[not found] ` <20150909140448.GI4973-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-09-10 1:27 ` Ong, Boon Leong
2015-09-10 1:27 ` Ong, Boon Leong
-- strict thread matches above, loose matches on Subject: below --
2015-08-21 11:34 [PATCH v5 0/2] Enable capsule loader interface for " Kweh, Hock Leong
2015-08-21 11:34 ` [PATCH v5 2/2] efi: a misc char interface for user to update " Kweh, Hock Leong
2015-08-27 14:43 ` Matt Fleming
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=20150909140448.GI4973@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=boon.leong.ong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=hock.leong.kweh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=roy.franz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=semen.protsenko-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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 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.