linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: linux-next: Tree for Feb 13
Date: Mon, 13 Feb 2012 15:01:15 -0800	[thread overview]
Message-ID: <1329174075.4431.33.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20120213172613.be7258c4c34431ff31dcbbef@canb.auug.org.au>

Hi Stephen,

On Mon, 2012-02-13 at 17:26 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20120210:
> 
> New trees: iscsi, dma-mapping
> 

<SNIP>

Just FYI that I think djbw's (Cc'ed) new tree is supposed to be 'isci'
instead of 'iscsi'..

iscsi           git     git://git.kernel.org/pub/scm/linux/kernel/git/djbw/isci.git#all

Thanks,

--nab

  parent reply	other threads:[~2012-02-13 23:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  6:26 linux-next: Tree for Feb 13 Stephen Rothwell
2012-02-13 17:46 ` linux-next: Tree for Feb 13 (staging/zsmalloc) Randy Dunlap
2012-02-13 17:51 ` linux-next: Tree for Feb 13 (ata/libata-acpi.c) Randy Dunlap
2012-02-13 18:00 ` linux-next: Tree for Feb 13 (staging/zsmalloc 2) Randy Dunlap
2012-02-13 18:11 ` linux-next: Tree for Feb 13 (sound/soc) Randy Dunlap
2012-02-13 22:10 ` linux-next: Tree for Feb 13 Grant Likely
2012-02-13 23:01 ` Nicholas A. Bellinger [this message]
2012-02-13 23:43   ` Stephen Rothwell
2012-02-13 23:32 ` Jack Stone
2012-02-13 23:56 ` Jack Stone
2013-02-13  8:35 Stephen Rothwell
2014-02-13  5:38 Stephen Rothwell
2015-02-13  5:56 Stephen Rothwell
2015-02-13 11:03 ` Sabrina Dubroca
2017-02-13  6:36 Stephen Rothwell
2018-02-13  4:15 Stephen Rothwell
2019-02-13  7:39 Stephen Rothwell
2020-02-13  3:52 Stephen Rothwell
2023-02-13  4:33 Stephen Rothwell
2024-02-13  4:08 Stephen Rothwell

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=1329174075.4431.33.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).