All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] firewire: cdev: ABI documentation enhancements
Date: Sat, 9 Jul 2011 17:05:06 +0200	[thread overview]
Message-ID: <20110709170506.5e036f86@stein> (raw)
In-Reply-To: <20110709164737.53cf7801@stein>

On Jul 09 Stefan Richter wrote:
> @@ -672,7 +661,7 @@ struct fw_cdev_remove_descriptor {
>   * @handle:	Handle to context, written back by kernel
>   *
>   * Prior to sending or receiving isochronous I/O, a context must be created.
> - * The context records information about the transmit or receive configuration
> + * The context records information about the transmit or receive Configuration
>   * and typically maps to an underlying hardware resource.  A context is set up
>   * for either sending or receiving.  It is bound to a specific isochronous
>   * @channel.

Disregard this hunk.
-- 
Stefan Richter
-=====-==-== -=== -=--=
http://arcgraph.de/sr/

      parent reply	other threads:[~2011-07-09 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 14:42 [PATCH] firewire: cdev: return -ENOTTY for unimplemented ioctls, not -EINVAL Stefan Richter
2011-07-09 14:43 ` [PATCH] firewire: cdev: prevent race between first get_info ioctl and bus reset event queuing Stefan Richter
2011-07-09 14:47   ` [PATCH] firewire: cdev: ABI documentation enhancements Stefan Richter
2011-07-09 14:48     ` [PATCH] firewire: document the sysfs ABIs Stefan Richter
2011-07-09 15:05     ` Stefan Richter [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=20110709170506.5e036f86@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --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 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.