linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the scsi tree
Date: Fri, 23 Mar 2012 11:30:09 -0400	[thread overview]
Message-ID: <4F6C9701.50103@pobox.com> (raw)
In-Reply-To: <CACVxJT-MgLO5aLiRuSR=61nea47V27vsXJB9St20J6G6hSe8xw@mail.gmail.com>

On 03/23/2012 06:26 AM, Alexey Dobriyan wrote:
> On Fri, Mar 23, 2012 at 7:50 AM, Benjamin Herrenschmidt
> <benh@kernel.crashing.org>  wrote:
>> On Fri, 2012-03-23 at 13:00 +1100, Stephen Rothwell wrote:
>>> Hi James,
>>>
>>> After merging the scsi tree, today's linux-next build (powerpc
>>> ppc64_defconfig) failed like this:
>>>
>>> drivers/ata/sata_svw.c: In function 'k2_sata_proc_open':
>>> drivers/ata/sata_svw.c:327:2: error: implicit declaration of function 'PDE' [-Werror=implicit-function-declaration]
>>> drivers/ata/sata_svw.c:327:56: error: invalid type argument of '->' (have 'int')
>>> drivers/ata/sata_svw.c:328:1: warning: control reaches end of non-void function [-Wreturn-type]
>>>
>>> Caused by commit 343ac4b031a7 ("[SCSI] sata_svw: convert to scsi proc_ops").
>>>
>>> I have used the scsi tree from next-20120322 for today.
>>
>> 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 ?
>
> Your email was not mentioned in changelogs for 6 years nor the driver
> has specific MAINTAINERS entry.


At the top of drivers/ata/sata_svw.c, we find:

  *  Maintained by: Benjamin Herrenschmidt <benh@kernel.crashing.org> and
  *                 Jeff Garzik <jgarzik@pobox.com>
  *                  Please ALWAYS copy linux-ide@vger.kernel.org
  *                  on emails.

and in MAINTAINERS we also find

SERIAL ATA (SATA) SUBSYSTEM
M:      Jeff Garzik <jgarzik@pobox.com>
L:      linux-ide@vger.kernel.org
T:      git 
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
S:      Supported
F:      drivers/ata/

None of these addresses, nor LKML, were copied.  Please do so in the future.

	Jeff




  reply	other threads:[~2012-03-23 15:30 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  2:00 linux-next: build failure after merge of the scsi tree Stephen Rothwell
2012-03-23  4:50 ` Benjamin Herrenschmidt
2012-03-23  8:14   ` James Bottomley
2012-03-23  8:53     ` Benjamin Herrenschmidt
2012-03-23  9:01       ` James Bottomley
2012-03-23 15:22         ` Jeff Garzik
2012-03-23 10:26   ` Alexey Dobriyan
2012-03-23 15:30     ` Jeff Garzik [this message]
2012-03-23  8:20 ` James Bottomley
2012-03-23  9:24   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2019-03-20  0:48 Stephen Rothwell
2017-08-28  8:02 Stephen Rothwell
2017-02-06  5:04 Stephen Rothwell
2017-02-13  0:32 ` Stephen Rothwell
2017-02-13 16:18   ` Jens Axboe
2016-12-23  0:45 Stephen Rothwell
2016-12-23  0:56 ` James Bottomley
     [not found]   ` <20161224123853.08284e8a@canb.auug.org.au>
2016-12-24 10:15     ` Ingo Molnar
2016-12-24 10:44       ` Stephen Rothwell
2016-12-24 11:46     ` Thomas Gleixner
2016-12-24 16:48       ` James Bottomley
2015-11-13  1:35 Stephen Rothwell
2015-11-13  8:32 ` Sreekanth Reddy
2015-06-02  8:06 Stephen Rothwell
2015-06-02 15:02 ` James Bottomley
2015-02-04  6:29 Stephen Rothwell
2015-02-04  6:47 ` Joe Perches
2015-02-04 15:26 ` James Bottomley
2014-11-10  6:15 Stephen Rothwell
2014-11-10  6:27 ` Anish Bhatt
2014-11-10 13:46   ` Christoph Hellwig
2014-11-10 15:21     ` James Bottomley
2014-11-10 15:48       ` Christoph Hellwig
2014-11-10 15:50         ` James Bottomley
2014-11-10 16:01           ` Christoph Hellwig
2014-11-04  4:43 Stephen Rothwell
2014-11-04  7:07 ` Hannes Reinecke
2014-11-05  4:48   ` Stephen Rothwell
2014-11-03  2:52 Stephen Rothwell
2014-11-03  7:51 ` Hannes Reinecke
2014-11-03 18:31   ` Christoph Hellwig
2014-09-26  8:34 Stephen Rothwell
2014-09-26  8:36 ` Christoph Hellwig
2014-09-26  9:57   ` James Bottomley
2014-09-26 12:43     ` Brian King
2013-01-12  2:23 wenxiong
2013-01-11  1:03 Stephen Rothwell
2013-01-11  7:34 ` James Bottomley
2013-01-11 15:27   ` Brian King
2013-01-11 15:37     ` James Bottomley
2013-01-11 16:05       ` Greg KH
2013-01-11 17:35         ` Brian King
2013-01-11 18:04           ` James Bottomley
2012-07-20  0:41 Stephen Rothwell
2012-07-20  8:50 ` James Bottomley
2012-03-26  1:17 Stephen Rothwell
2012-03-26  7:57 ` James Bottomley
2012-03-26 14:07   ` Greg KH
2012-03-27  7:29     ` James Bottomley
2012-03-27 22:17     ` Alexey Dobriyan
2012-03-27 22:22       ` Greg KH
2012-03-27 22:35         ` Alexey Dobriyan
2012-03-27 22:39           ` Alexey Dobriyan
2012-03-28 23:54             ` Greg KH
2012-03-29 19:38             ` Greg KH
2012-03-28 23:52           ` Greg KH
2012-03-29  7:32             ` Gerard Snitselaar
2012-03-29  8:25               ` Stephen Rothwell
2012-03-29  8:35                 ` James Bottomley
2012-03-29  9:03                 ` Gerard Snitselaar
2012-03-29 16:15                   ` Greg KH
2011-12-15  1:58 Stephen Rothwell
2011-12-15  6:53 ` James Bottomley
2011-08-29  2:09 Stephen Rothwell
2011-08-29  7:17 ` James Bottomley
2011-08-29  8:07   ` Giridhar Malavali
2011-05-27  3:25 Stephen Rothwell
2011-05-27 13:47 ` James Bottomley
2010-10-26  0:19 Stephen Rothwell
2010-10-26 15:50 ` James Bottomley
2010-02-10  1:33 Stephen Rothwell
2010-02-10 22:16 ` James Bottomley
2010-02-10 23:11   ` Stephen Rothwell
2010-02-16  0:38   ` 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=4F6C9701.50103@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=adobriyan@gmail.com \
    --cc=benh@kernel.crashing.org \
    --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).