All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] block/xd.c: fix brace typo
Date: Tue, 22 Jun 2010 19:24:18 +0200	[thread overview]
Message-ID: <4C20F1C2.5020009@kernel.dk> (raw)
In-Reply-To: <20100622090343.d921a70c.randy.dunlap@oracle.com>

On 2010-06-22 18:03, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Fix extra brace typo that is causing build errors

Thanks Randy, applied.

-- 
Jens Axboe

      reply	other threads:[~2010-06-22 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  6:05 linux-next: Tree for June 22 Stephen Rothwell
2010-06-22  7:53 ` Geert Uytterhoeven
2010-06-22 10:22   ` Stephen Rothwell
2010-06-22 15:30 ` linux-next: Tree for June 22 (staging/spectra) Randy Dunlap
2010-06-22 15:59   ` Randy Dunlap
2010-06-22 20:42     ` Greg KH
2010-06-22 16:03 ` [PATCH -next] block/xd.c: fix brace typo Randy Dunlap
2010-06-22 17:24   ` Jens Axboe [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=4C20F1C2.5020009@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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.