From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: linux-next: build failure after merge of the scsi tree Date: Fri, 23 Mar 2012 19:53:52 +1100 Message-ID: <1332492832.2882.4.camel@pasglop> References: <20120323130031.c097ca3755de5ff5879504e1@canb.auug.org.au> <1332478202.2882.2.camel@pasglop> <1332490486.2801.1.camel@dabdike.int.hansenpartnership.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1332490486.2801.1.camel@dabdike.int.hansenpartnership.com> Sender: linux-kernel-owner@vger.kernel.org To: James Bottomley Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Alexey Dobriyan , Jeff Garzik List-Id: linux-next.vger.kernel.org On Fri, 2012-03-23 at 08:14 +0000, James Bottomley wrote: > > Additionally, I am the author and maintainer of that driver and I > don't > > remember ever being CCed on that patch ... or did I miss it ? > > You missed it ... I added you and Jeff for automatic cc's when the > commit hit the scsi tree. > > This is the mail log: > > Mar 22 07:53:17 bedivere postfix/smtp[14322]: C3A1F8EE136: > to=, > relay=gate.crashing.org[63.228.1.57]:25, delay=2.7, > delays=0.13/0.12/1.3/1.2, dsn=2.0.0, status=sent (250 2.0.0 > q2MErGNT019145 Message accepted for delivery) Allright, Mar 22, that's yesterday (.au time)... that's a short time between notifying the maintainer and going into -next :-) No biggie, I'll have a look next week, it's just annoying to get build failure reports from Stephen about drivers I own for patches I never heard about ... Cheers, Ben.