From: Josh Triplett <josh@joshtriplett.org>
To: Shakthi Kannan <shakthimaan@gmail.com>
Cc: Christopher Li <sparse@chrisli.org>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Updated __nocast vs __bitwise documentation
Date: Thu, 10 May 2012 11:24:40 -0700 [thread overview]
Message-ID: <20120510182440.GA19991@leaf> (raw)
In-Reply-To: <CABG-yt2yVwF76vHitm-KzKLV4kQ205hEMTCeRcsJF9-doWvW6w@mail.gmail.com>
On Thu, May 10, 2012 at 04:36:28PM +0530, Shakthi Kannan wrote:
> Source: https://lkml.org/lkml/2012/3/22/409
I've found lkml.org somewhat unreliable. I'd suggest liking to
http://mid.gmane.org/<the-message-ID> ; in this case,
http://mid.gmane.org/CA+55aFzbhYvw7Am9EYgatpjTknBFm9eq+3jBWQHkSCUpnb3HRQ@mail.gmail.com
- Josh Triplett
next prev parent reply other threads:[~2012-05-10 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 6:54 [PATCH] Updated __nocast vs __bitwise documentation Shakthi Kannan
2012-05-10 10:50 ` Christopher Li
2012-05-10 11:06 ` Shakthi Kannan
2012-05-10 11:42 ` Christopher Li
2012-05-10 18:24 ` Josh Triplett [this message]
2012-05-15 10:06 ` Shakthi Kannan
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=20120510182440.GA19991@leaf \
--to=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=shakthimaan@gmail.com \
--cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).