All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: NeilBrown <neilb@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux RAID <linux-raid@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST - 3.15] to md bugfixes, tagged for -stable
Date: Tue, 3 Jun 2014 09:41:56 +1000	[thread overview]
Message-ID: <20140603094156.40550049@notabene.brown> (raw)
In-Reply-To: <20140603093833.1bca3dfb@notabene.brown>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

On Tue, 3 Jun 2014 09:38:33 +1000 NeilBrown <neilb@suse.de> wrote:

> 
> Hi Linus,
> If these could be pulled into 3.15, I'd appreciate it.
> Otherwise they end up in 3.15.y for some y eventually.
> 
> Thanks,
> NeilBrown
> 
> 
> The following changes since commit c7208164e66f63e3ec1759b98087849286410741:
> 
>   Linux 3.15-rc7 (2014-05-25 16:06:00 -0700)
> 
> are available in the git repository at:
> 
>   git://neil.brown.name/md 

Hm.... looks like a bug in git 3.0.  It didn't add the tag name for me like
it used to.

That should be

  git://neil.brown.name/md tags/md/3.15-fixes

NeilBrown

> 
> for you to fetch changes up to 2ac295a544dcae9299cba13ce250419117ae7fd1:
> 
>   md: always set MD_RECOVERY_INTR when interrupting a reshape thread. (2014-05-29 16:59:06 +1000)
> 
> ----------------------------------------------------------------
> NeilBrown (2):
>       md: always set MD_RECOVERY_INTR when aborting a reshape or other "resync".
>       md: always set MD_RECOVERY_INTR when interrupting a reshape thread.
> 
>  drivers/md/md.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2014-06-02 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 23:38 [PULL REQUEST - 3.15] to md bugfixes, tagged for -stable NeilBrown
2014-06-02 23:41 ` NeilBrown [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=20140603094156.40550049@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.