From: Valdis.Kletnieks@vt.edu
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Daniel Hazelton <dhazelton@enter.net>,
Marat Buharov <marat.buharov@gmail.com>,
Parav K Pandit <Parav_Pandit@mindtree.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: assembly code in the loadable kernel module
Date: Tue, 01 May 2007 09:08:34 -0400 [thread overview]
Message-ID: <17221.1178024914@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 27 Apr 2007 17:06:48 EDT." <Pine.LNX.4.61.0704271658240.5071@chaos.analogic.com>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Fri, 27 Apr 2007 17:06:48 EDT, "linux-os (Dick Johnson)" said:
> if(strchr(buf, 'Z'-64) || strchr(buf, 'D'-64))
This probably isn't UTF-8 safe... :)
> Anything after ^D or ^Z doesn't get copied to the list. Something like
> this needs to be done because it's gonna get a whole lot worse because
> all the 'IT' people read the same rags -- so they think that "naked"
> email fails the "due diligence" test. Honest, I'm not making that up!
And here I thought blindly slapping that disclaimer on *everything*, whether
or not it actually called for it, failed "due diligence". Ain't much diligence,
due or otherwise, in evidence when a "This contains confidential" sticker
gets posted to a worldwide public mailing list...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-05-01 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 8:45 Parav K Pandit
2007-04-27 9:40 ` Jan Engelhardt
2007-04-27 10:59 ` Sam Ravnborg
2007-04-27 11:27 ` linux-os (Dick Johnson)
2007-04-27 11:57 ` Marat Buharov
2007-04-27 12:11 ` Robert P. J. Day
2007-04-27 16:12 ` Daniel Hazelton
2007-04-27 21:06 ` linux-os (Dick Johnson)
2007-05-01 13:08 ` Valdis.Kletnieks [this message]
2007-04-27 21:31 ` Lee Revell
2007-04-27 21:55 ` Alan Cox
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=17221.1178024914@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=Parav_Pandit@mindtree.com \
--cc=dhazelton@enter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=marat.buharov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®