public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bob Pearson" <rpearson@systemfabricworks.com>
To: "'Randy Dunlap'" <rdunlap@xenotime.net>
Cc: <linux-kernel@vger.kernel.org>, <linux@horizon.com>,
	<joakim.tjernlund@transmode.se>, <fzago@systemfabricworks.com>,
	<akpm@linux-foundation.org>
Subject: RE: [patch v3 1/7] crc32: move-to-documentation.diff
Date: Tue, 9 Aug 2011 01:00:20 -0500	[thread overview]
Message-ID: <00d301cc5659$9f6b01d0$de410570$@systemfabricworks.com> (raw)
In-Reply-To: <d8d606c9a7ca85a50ef008b7697c84bc.squirrel@xenotime.net>

> -----Original Message-----
> From: Randy Dunlap [mailto:rdunlap@xenotime.net]
> Sent: Tuesday, August 09, 2011 12:24 AM
> To: Bob Pearson
> Cc: linux-kernel@vger.kernel.org; linux@horizon.com;
> joakim.tjernlund@transmode.se; fzago@systemfabricworks.com;
> rpearson@systemfabricworks.com; akpm@linux-foundation.org
> Subject: Re: [patch v3 1/7] crc32: move-to-documentation.diff
> 
> On Mon, August 8, 2011 10:15 pm, Bob Pearson wrote:
> > Moved a nice but long comment from lib/crc32.c to
> Documentation/crc32.txt
> > where it will more likely get read.
> >
> > Signed-off-by: Bob Pearson <rpearson@systemfabricworks.com>
> >
> > ---
> >  Documentation/crc32.txt |  129
> > ++++++++++++++++++++++++++++++++++++++++++++++++
> >  lib/crc32.c             |  127
> > -----------------------------------------------
> >  2 files changed, 129 insertions(+), 127 deletions(-)
> 
> Please update Documentation/00-INDEX with this new
> file's entry.

On its way. Thanks

> 
> Thanks.
> 
> --
> ~Randy


      reply	other threads:[~2011-08-09  6:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09  5:15 [patch v3 1/7] crc32: move-to-documentation.diff Bob Pearson
2011-08-09  5:23 ` Randy Dunlap
2011-08-09  6:00   ` Bob Pearson [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='00d301cc5659$9f6b01d0$de410570$@systemfabricworks.com' \
    --to=rpearson@systemfabricworks.com \
    --cc=akpm@linux-foundation.org \
    --cc=fzago@systemfabricworks.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=rdunlap@xenotime.net \
    /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