public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Vitaliy Ivanov <vitalivanov@gmail.com>
Cc: zaitcev@redhat.com, gregkh@suse.de,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [2.4 patch] Port of adutux driver from 2.6 kernel to 2.4.
Date: Tue, 16 Oct 2007 17:41:38 +0200	[thread overview]
Message-ID: <20071016154138.GA23326@1wt.eu> (raw)
In-Reply-To: <1192542889.29039.66.camel@dell1.softservecom.com>

On Tue, Oct 16, 2007 at 04:54:49PM +0300, Vitaliy Ivanov wrote:
> Willy,
> 
> On Mon, 2007-10-15 at 01:39, Willy Tarreau wrote:
> 
> > That's what I've seen. I can propose you something (unless someone
> > else raises his hand saying "no") : you update your patch with a
> > short description of what the hardware module is supposed to be used
> > for, and you accept to step up as the maintainer for this backport,
> > which will imply that you put your name and mail in the MAINTAINERS
> > file. That way, if you're the only user, nobody will be annoyed, and
> > if there are other users and some of them have problems, I don't waste
> > my time on something I don't know at all. If you agree with this deal
> > (which I think is fair), then I'm willing to merge your patch into
> > 2.4.36-pre.
> 
> It's completely fair. I spent some time on lkml and I liked it.
> I've a device and I can check/correct any issue we'll have with it(hope there won't be any;)).
> So it's OK for me to be a maintainer for this driver.
> 
> Here is final patch with all issues corrected.
> 
> Again, comments are welcomed.

OK, I have no objection, but please apply the fixes the le16 problem as
suggested by Pete and Greg first. Also, you will probably receive more
comments, and/or criticisms from further reviews. This is normal and
expected. You just have to fix your code so that it can be merged.

> adutux is a simple Linux device driver for ADU boards from Ontrak Control Systems. 
> The adutux driver exposes standard open/close/read/write API's to the user application.

If this is going to be the commit message, please reduce lines to less
than 70 chars, and also enumerate the supportd devices and the one you
performed the tests with. It helps a lot when users encounter problems.

Also, if you did not (I forgot to check), please ensure that the adutux
maintainer in 2.6 is CC'd.

Last but not least, please remove the "KERNELS/" path component from
your next diff.

Thanks,
Willy


  reply	other threads:[~2007-10-16 15:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 17:37 [2.4 patch] Port of adutux driver from 2.6 kernel to 2.4 Vitaliy Ivanov
2007-10-14 18:25 ` Willy Tarreau
2007-10-14 20:45   ` Vitaliy Ivanov
2007-10-14 22:39     ` Willy Tarreau
2007-10-16 13:54       ` Vitaliy Ivanov
2007-10-16 15:41         ` Willy Tarreau [this message]
2007-10-16 17:56           ` Pete Zaitcev
2007-10-16 18:22             ` Vitaliy Ivanov
2007-10-16 18:24             ` Willy Tarreau
2007-10-16 18:24           ` Vitaliy Ivanov
2007-10-17 18:12             ` Vitaliy Ivanov
2007-10-19 15:26               ` Vitaliy Ivanov
2007-10-19 16:53                 ` Pete Zaitcev
2007-10-19 17:40                   ` Vitaliy Ivanov
2007-10-23  3:45                     ` Pete Zaitcev
2007-11-04 14:05                       ` Willy Tarreau
2007-11-05  9:32                         ` Vitaliy Ivanov
2007-11-05  9:36                           ` Willy Tarreau
2007-10-16 17:52         ` Pete Zaitcev
2007-10-15 17:30     ` Pete Zaitcev
2007-10-15 20:04       ` Vitaliy Ivanov
2007-10-16 13:48       ` Vitaliy Ivanov
2007-10-16 14:59         ` Greg KH

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=20071016154138.GA23326@1wt.eu \
    --to=w@1wt.eu \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=vitalivanov@gmail.com \
    --cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox