public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Cashin <ecashin@coraid.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, ecashin@coraid.com
Subject: [PATCH 0/2] aoe: remove too-strict BUG from aoedev teardown and update udev example
Date: Wed, 28 Aug 2013 11:41:06 -0400	[thread overview]
Message-ID: <cover.1377185392.git.ecashin@coraid.com> (raw)

This patch series applies to linux-next/akpm fetched 22 August, commit
a187db44dd9b24a9eed2141af962306a36935423.  Yesterday's linux-next/akpm
has no updates to the aoe files that could conflict, though.

Ed L. Cashin (2):
  aoe: do not BUG if memory pressure prevented debugfs file creation
  aoe: remove do-nothing NAME="%k" term from example udev rules

 Documentation/aoe/udev.txt |    2 +-
 drivers/block/aoe/aoeblk.c |    1 -
 2 files changed, 1 insertions(+), 2 deletions(-)


             reply	other threads:[~2013-08-28 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 15:41 Ed Cashin [this message]
2013-08-28 15:41 ` [PATCH 1/2] aoe: do not BUG if memory pressure prevented debugfs file creation Ed Cashin
2013-08-28 15:43 ` [PATCH 2/2] aoe: remove do-nothing NAME="%k" term from example udev rules Ed Cashin

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=cover.1377185392.git.ecashin@coraid.com \
    --to=ecashin@coraid.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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