From: Christoph Hellwig <hch@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [ANNOUNCE] scsi patch queue tree updated
Date: Mon, 4 Aug 2014 04:34:04 -0700 [thread overview]
Message-ID: <20140804113404.GA11377@infradead.org> (raw)
In-Reply-To: <20140804213059.32fd25d5@canb.auug.org.au>
On Mon, Aug 04, 2014 at 09:30:59PM +1000, Stephen Rothwell wrote:
> You realise that neither of these in linux-next as the scsi-core and
> scsi-drivers trees had for-3.16 branches in the last round. I assume I
> should just drop these trees completely from linux-next?
Well, they get pulled in through James, so you can drop them for now.
I mostly put you on Cc so you could comment wether there are any hard
rules on how long even those simple fixes should be in linux-next. I
know you've put up stats for a few of the last merge windows about
patches that weren't in linux-next, so there's been some tracking of it
for sure.
next prev parent reply other threads:[~2014-08-04 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 13:40 [ANNOUNCE] scsi patch queue tree updated Christoph Hellwig
2014-08-01 12:20 ` Christoph Hellwig
2014-08-01 20:32 ` James Bottomley
2014-08-04 11:11 ` Christoph Hellwig
2014-08-04 11:30 ` Stephen Rothwell
2014-08-04 11:34 ` Christoph Hellwig [this message]
2014-08-04 11:39 ` Stephen Rothwell
2014-08-04 14:20 ` James Bottomley
2014-08-14 12:54 ` Christoph Hellwig
2014-08-14 17:47 ` James Bottomley
2014-08-15 19:25 ` Christoph Hellwig
2014-08-15 19:32 ` James Bottomley
2014-09-15 22:58 ` Christoph Hellwig
2014-09-16 21:37 ` Christoph Hellwig
2014-09-16 21:44 ` James Bottomley
2014-12-30 13:02 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2014-07-18 10:02 Christoph Hellwig
2014-07-25 21:19 ` Christoph Hellwig
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=20140804113404.GA11377@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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).