public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@suse.de>, Nigel Kukard <nkukard@lbsd.net>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] DVD+RW support for 2.6.7-bk13
Date: 01 Sep 2004 20:40:42 +0200	[thread overview]
Message-ID: <m34qmhest1.fsf@telia.com> (raw)
In-Reply-To: <m2hdsr6du0.fsf@telia.com>

Peter Osterlund <petero2@telia.com> writes:

> This patch adds support for using DVD+RW drives as writable block
> devices under the 2.6.7-bk13 kernel.
> 
> The patch is based on work from:
> 
>         Andy Polyakov <appro@fy.chalmers.se> - Wrote the 2.4 patch
>         Nigel Kukard <nkukard@lbsd.net> - Initial porting to 2.6.x
...
>  linux-petero/drivers/cdrom/cdrom.c |   80 +++++++++++++++++++++++++++++++++++++
>  linux-petero/drivers/ide/ide-cd.c  |    2 
>  linux-petero/drivers/scsi/sr.c     |    1 
>  linux-petero/include/linux/cdrom.h |    2 

Nigel pointed out that the earlier patches contained attributions that
are not present in this patch. The 2.4 patch contains:

  Nov 5 2001, Aug 8 2002. Modified by Andy Polyakov
  <appro@fy.chalmers.se> to support MMC-3 complaint DVD+RW units.

and Nigel changed it to this in his 2.6 patch:

  Modified by Nigel Kukard <nkukard@lbsd.net> - support DVD+RW
  2.4.x patch by Andy Polyakov <appro@fy.chalmers.se>

The patch I sent you deleted most of the earlier work and moved the
rest to cdrom.c, but the comments were not moved over, since the
earlier authors didn't modify cdrom.c.

Nigel wants to get credit for his work though, so were should we put
those messages? Is this patch acceptable?


 linux-petero/drivers/cdrom/cdrom.c |    6 ++++++
 1 files changed, 6 insertions(+)

diff -puN drivers/cdrom/cdrom.c~packet-copyright drivers/cdrom/cdrom.c
--- linux/drivers/cdrom/cdrom.c~packet-copyright	2004-09-01 20:03:13.075394816 +0200
+++ linux-petero/drivers/cdrom/cdrom.c	2004-09-01 20:31:57.282275528 +0200
@@ -234,6 +234,12 @@
   -- Mt Rainier support
   -- DVD-RAM write open fixes
 
+  Nov 5 2001, Aug 8 2002. Modified by Andy Polyakov
+  <appro@fy.chalmers.se> to support MMC-3 compliant DVD+RW units.
+
+  Modified by Nigel Kukard <nkukard@lbsd.net> - support DVD+RW
+  2.4.x patch by Andy Polyakov <appro@fy.chalmers.se>
+
 -------------------------------------------------------------------------*/
 
 #define REVISION "Revision: 3.20"
_

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340

  parent reply	other threads:[~2004-09-01 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 13:45 [PATCH] DVD+RW support for 2.6.7-bk13 Peter Osterlund
2004-07-01 16:16 ` Wakko Warner
2004-07-01 21:02   ` Peter Osterlund
2004-07-01 23:29     ` Wakko Warner
2004-07-02 14:58       ` Peter Osterlund
     [not found]         ` <20040702162028.28765ce1.akpm@osdl.org>
2004-07-03  0:22           ` Peter Osterlund
2004-09-01 18:40 ` Peter Osterlund [this message]
2004-09-01 18:47   ` Nigel Kukard

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=m34qmhest1.fsf@telia.com \
    --to=petero2@telia.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nkukard@lbsd.net \
    /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