public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, ecashin@coraid.com
Subject: [GIT PATCH] AOE fixes and update for 2.6.19-rc2
Date: Wed, 18 Oct 2006 13:04:33 -0700	[thread overview]
Message-ID: <20061018200433.GA10079@kroah.com> (raw)

Here are some ATA over Ethernet patches against your current git tree.
They all have been in the -mm tree for a few months.

Please pull from:
	rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/aoe-2.6.git/
or from:
	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/aoe-2.6.git/
if it isn't synced up yet.

The full patch series will sent to the linux-kernel mailing list, if
anyone wants to see them.

thanks,

greg k-h


 drivers/block/aoe/aoe.h     |   30 ++--
 drivers/block/aoe/aoeblk.c  |   44 +++---
 drivers/block/aoe/aoechr.c  |   18 +--
 drivers/block/aoe/aoecmd.c  |  303 ++++++++++++++++++++++++++++---------------
 drivers/block/aoe/aoedev.c  |   52 +++++--
 drivers/block/aoe/aoemain.c |   10 +
 drivers/block/aoe/aoenet.c  |    9 +
 7 files changed, 287 insertions(+), 179 deletions(-)

---------------

Ed L Cashin:
      aoe: eliminate isbusy message
      aoe: update copyright date
      aoe: remove unused NARGS enum
      aoe: zero copy write 1 of 2
      aoe: jumbo frame support 1 of 2
      aoe: clean up printks via macros
      aoe: jumbo frame support 2 of 2
      aoe: improve retransmission heuristics
      aoe: zero copy write 2 of 2
      aoe: module parameter for device timeout
      aoe: use bio->bi_idx
      aoe: remove sysfs comment
      aoe: update driver version
      aoe: revert printk macros

Greg Kroah-Hartman:
      aoe: fix sysfs_create_file warnings


             reply	other threads:[~2006-10-18 20:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 20:04 Greg KH [this message]
2006-10-18 20:08 ` [PATCH 1/15] aoe: eliminate isbusy message Greg KH
2006-10-18 20:08   ` [PATCH 2/15] aoe: update copyright date Greg KH
2006-10-18 20:08     ` [PATCH 3/15] aoe: remove unused NARGS enum Greg KH
2006-10-18 20:08       ` [PATCH 4/15] aoe: zero copy write 1 of 2 Greg KH
2006-10-18 20:08         ` [PATCH 5/15] aoe: jumbo frame support " Greg KH
2006-10-18 20:08           ` [PATCH 6/15] aoe: clean up printks via macros Greg KH
2006-10-18 20:08             ` [PATCH 7/15] aoe: jumbo frame support 2 of 2 Greg KH
2006-10-18 20:08               ` [PATCH 8/15] aoe: improve retransmission heuristics Greg KH
2006-10-18 20:09                 ` [PATCH 9/15] aoe: zero copy write 2 of 2 Greg KH
2006-10-18 20:09                   ` [PATCH 10/15] aoe: module parameter for device timeout Greg KH
2006-10-18 20:09                     ` [PATCH 11/15] aoe: use bio->bi_idx Greg KH
2006-10-18 20:09                       ` [PATCH 12/15] aoe: remove sysfs comment Greg KH
2006-10-18 20:09                         ` [PATCH 13/15] aoe: update driver version Greg KH
2006-10-18 20:09                           ` [PATCH 14/15] aoe: revert printk macros Greg KH
2006-10-18 20:09                             ` [PATCH 15/15] aoe: fix sysfs_create_file warnings Greg KH

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=20061018200433.GA10079@kroah.com \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=ecashin@coraid.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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