All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	"James E.J. Bottomley" <JBottomley@odin.com>,
	Ondrej Zary <linux@rainbow-software.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org, Hannes Reinecke <hare@suse.com>
Subject: Re: [patch RESEND] atp870u: 64 bit bug in atp885_init()
Date: Wed, 9 Dec 2015 19:37:32 +0000	[thread overview]
Message-ID: <20151209193732.5940e706@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20151209182822.GC5284@mwanda>

> You should just delete that code along with the Kconfig and Makefile
> entries.  Don't bother moving it to staging.  The move to staging is
> supposed to give people one last chance to yell if they absolutely need
> the code.  No one has compiled this code for years so no one will miss
> it.

And for stuff which might be worth saving (eg something that looks rather
broken but has possibly got users) the driver goes into staging
in its own directory and the Makefile and Kconfig entry for it move into
the staging directory with the hope that someone screams and maintains it.

Alan


WARNING: multiple messages have this Message-ID (diff)
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	"James E.J. Bottomley" <JBottomley@odin.com>,
	Ondrej Zary <linux@rainbow-software.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org, Hannes Reinecke <hare@suse.com>
Subject: Re: [patch RESEND] atp870u: 64 bit bug in atp885_init()
Date: Wed, 09 Dec 2015 19:37:32 +0000	[thread overview]
Message-ID: <20151209193732.5940e706@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20151209182822.GC5284@mwanda>

> You should just delete that code along with the Kconfig and Makefile
> entries.  Don't bother moving it to staging.  The move to staging is
> supposed to give people one last chance to yell if they absolutely need
> the code.  No one has compiled this code for years so no one will miss
> it.

And for stuff which might be worth saving (eg something that looks rather
broken but has possibly got users) the driver goes into staging
in its own directory and the Makefile and Kconfig entry for it move into
the staging directory with the hope that someone screams and maintains it.

Alan


  reply	other threads:[~2015-12-09 19:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04  9:50 [patch] [SCSI] atp870u: 64 bit bug in probe() Dan Carpenter
2013-09-04  9:50 ` Dan Carpenter
2015-07-29 21:36 ` Dan Carpenter
2015-07-29 21:36   ` Dan Carpenter
2015-07-30  6:54   ` Hannes Reinecke
2015-07-30  6:54     ` Hannes Reinecke
2015-12-09 10:24     ` [patch RESEND] atp870u: 64 bit bug in atp885_init() Dan Carpenter
2015-12-09 10:24       ` Dan Carpenter
2015-12-09 11:53       ` One Thousand Gnomes
2015-12-09 11:53         ` One Thousand Gnomes
2015-12-09 12:07         ` Ondrej Zary
2015-12-09 12:07           ` Ondrej Zary
2015-12-09 13:45         ` Dan Carpenter
2015-12-09 13:45           ` Dan Carpenter
2015-12-09 14:14           ` One Thousand Gnomes
2015-12-09 14:14             ` One Thousand Gnomes
2015-12-09 17:48             ` Dan Carpenter
2015-12-09 17:48               ` Dan Carpenter
2015-12-09 18:11               ` Julia Lawall
2015-12-09 18:11                 ` Julia Lawall
2015-12-09 18:28                 ` Dan Carpenter
2015-12-09 18:28                   ` Dan Carpenter
2015-12-09 19:37                   ` One Thousand Gnomes [this message]
2015-12-09 19:37                     ` One Thousand Gnomes
2018-02-15 23:44       ` Martin K. Petersen
2018-02-15 23:44         ` Martin K. Petersen
2018-03-02  2:11       ` Martin K. Petersen

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=20151209193732.5940e706@lxorguk.ukuu.org.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=JBottomley@odin.com \
    --cc=dan.carpenter@oracle.com \
    --cc=hare@suse.com \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=martin.petersen@oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.