public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Patches in 2.4.17-pre2 that aren't in 2.5.1-pre8
Date: Mon, 10 Dec 2001 18:22:31 +0100	[thread overview]
Message-ID: <3C14EF57.7070801@epfl.ch> (raw)
In-Reply-To: <Pine.LNX.4.21.0112101348470.25093-100000@freak.distro.conectiva>

Marcelo Tosatti wrote:

> Nicolas, 
> 
> Who is the maintainer of the driver ?


According to the 'MAINTAINERS' file, nobody. So everything related to 
the topic goes through you :-)


> Try to think from my side: I may have no hardware or time to test all
> patches which come to me.


That's why I did not pressed you. I sent you the patch something like 
two weeks ago, but I know you have a very big amount of email, and many 
other things to test/apply/reject/whatever. I just noticed that what I 
sent to you and Linus had been merged into the 2.5 tree, which motivated 
my reply, just to know the state of the


> Please, people, send this kind of driver changes to the people who know
> all hardware specific details.


As stated previously, there is no one for this... I only got positive 
feedback about my patches by Robert Love, but as you he did not have the 
hardware/time to test.


> If there is no maintainer for i810, I'll be glad to apply it on 2.4.18pre
> and wait for reports. Not going to be on 2.4.17, though.
> 

You're the boss ;-) As I said, I got at least 3 successful feedbacks for 
this patch, and the fact that Linux got it into the tree kinda confirms 
my thought that there might not be too many things broken in it. The 
choice of putting it into 2.4.17 or 2.4.18 is entirely yours, and I 
accept it whatever it is. Keep me informed ;-)

Best regards

-- 
Nicolas Aspert      Signal Processing Laboratory (LTS)
Swiss Federal Institute of Technology (EPFL)


  reply	other threads:[~2001-12-10 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <linux.kernel.E16DNNu-0001VB-00@the-village.bc.nu>
2001-12-10 11:43 ` Patches in 2.4.17-pre2 that aren't in 2.5.1-pre8 Nicolas Aspert
2001-12-10 15:53   ` Marcelo Tosatti
2001-12-10 17:22     ` Nicolas Aspert [this message]
2001-12-10 17:30     ` Alan Cox
2001-12-10 18:18     ` Robert Love
2001-12-10 17:13       ` Marcelo Tosatti
2001-12-10 18:47       ` Stephan von Krawczynski
2001-12-10  9:51 Adrian Bunk
2001-12-10 10:10 ` Alan Cox

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=3C14EF57.7070801@epfl.ch \
    --to=nicolas.aspert@epfl.ch \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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