From: Michal Marek <mmarek@suse.cz>
To: Jean Sacren <sakiwit@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] kconfig: Fix warning: ignoring return value of 'fwrite'
Date: Fri, 13 Aug 2010 00:50:31 +0200 [thread overview]
Message-ID: <20100812225031.GA19690@sepie.suse.cz> (raw)
In-Reply-To: <20100804220102.GA10534@mail.gmail.com>
On Wed, Aug 04, 2010 at 04:01:02PM -0600, Jean Sacren wrote:
> This fix facilitates fwrite() in both confdata.c and expr.c, either it
> succeeds in writing, or an error occurs, or the end of file is reached.
>
> Signed-off-by: Jean Sacren <sakiwit@gmail.com>
> Cc: stable <stable@kernel.org>
> ---
> scripts/kconfig/confdata.c | 6 +++---
> scripts/kconfig/expr.c | 2 +-
> scripts/kconfig/lkc.h | 7 +++++++
> 3 files changed, 11 insertions(+), 4 deletions(-)
I applied this and the second patch (sorry for the delay), but I dropped
the Cc: stable line. It's just a warning, nothing critical, and the
context is different in released kernels, so why bother Greg with
manually resolving conflicts.
Michal
prev parent reply other threads:[~2010-08-12 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 22:01 [PATCH 1/2] kconfig: Fix warning: ignoring return value of 'fwrite' Jean Sacren
2010-08-12 22:50 ` Michal Marek [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=20100812225031.GA19690@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=jkosina@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=sakiwit@gmail.com \
--cc=zippel@linux-m68k.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