From: Steve French <smfrench@austin.rr.com>
To: cherry@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: IA32 (2.6.10-rc3 - 2004-12-13.8.00) - 2 New warnings
Date: Sat, 18 Dec 2004 09:54:25 -0600 [thread overview]
Message-ID: <41C452B1.2070602@austin.rr.com> (raw)
I have fixed the two warnings you mention in the cifs code (how did you
generate those, I don't remember sparse emitting them). Although they
are low risk to include, I want to check out a recent change to
CIFSMBWrite (to allow smb bcc > 64K on write) before pushing them both.
next reply other threads:[~2004-12-18 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 15:54 Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 21:50 IA32 (2.6.10-rc3 - 2004-12-13.8.00) - 2 New warnings John Cherry
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=41C452B1.2070602@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=cherry@osdl.org \
--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 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.