From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-scsi <linux-scsi@vger.kernel.org>,
linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Temporary location for some of the SCSI trees
Date: Thu, 15 Sep 2011 10:37:33 -0500 [thread overview]
Message-ID: <1316101053.2983.42.camel@dabdike.hansenpartnership.com> (raw)
I've relocated the scsi-rc-fixes and scsi-misc trees on to my own
infrastructure while master.kernel.org is down. The locations are:
git://bedivere.hansenpartnership.com/git/scsi-rc-fixes-2.6.git
git://bedivere.hansenpartnership.com/git/scsi-misc-2.6.git
Since we're not currently using the scsi-postmerge tree, I haven't yet
done a replacement for it.
The current tree tops are
scsi-misc:
linus ba8f318 m68k: fix __page_to_pfn for a const struct page argument
master ebd1f64 [SCSI] scsi_dh_alua: Decrease retry interval
merge-base 7ca3c80 [SCSI] qla2xxx: Update version number to 8.03.07.07-k.
scsi-fixes:
linus 003f6c9 lib/sha1.c: quiet sparse noise about symbol not declared
master 610602f [SCSI] bnx2i: Fixed the endian on TTT for NOP out transmission
Could you add these to linux-next, please (until master comes back at least)?
For SCSI people, I still don't have any machinery for notifications or
an ftp site for the combined patch sets and change logs yet. When I get
that sorted out, I'll begin adding commits again.
Thanks,
James
next reply other threads:[~2011-09-15 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 15:37 James Bottomley [this message]
2011-09-16 0:57 ` Temporary location for some of the SCSI trees Stephen Rothwell
2011-10-11 16:52 ` SCSI trees moved back to kernel.org James Bottomley
2011-10-11 22:26 ` Stephen Rothwell
2011-10-11 22:35 ` James Bottomley
2011-10-11 22:44 ` Stephen Rothwell
2011-10-11 22:37 ` Sedat Dilek
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=1316101053.2983.42.camel@dabdike.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@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