From: "Scott Thompson" <postfail@hushmail.com>
To: jirislaby@gmail.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
dri-devel@lists.sourceforge.net
Subject: Re: [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode check
Date: Tue, 14 Aug 2007 04:01:40 +0000 [thread overview]
Message-ID: <20070814040141.5EE75DA81F@mailserver7.hushmail.com> (raw)
In-Reply-To: <20070813040530.9E0E9DA82E@mailserver8.hushmail.com>
On Mon, 13 Aug 2007 16:30:14 -0400 Jiri Slaby <jirislaby@gmail.com>
wrote:
>why dri-devel@lists.sourceforge.net?
>
David Airlie was listed as the owner on several of the files and in
maintainers for "DRM", which was my best to: guess for
/drivers/char/drm (which was patch 3 in this series).
If there was a better list, or just to linux-kernel, please let me
know as tracking down the 'right' list for these kernel-janitor
kind of tasks can be tricky....
---------------------------------------
Scott Thompson / postfail@hushmail.com
---------------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: "Scott Thompson" <postfail@hushmail.com>
To: <jirislaby@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
<dri-devel@lists.sourceforge.net>
Subject: Re: [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode check
Date: Tue, 14 Aug 2007 00:01:40 -0400 [thread overview]
Message-ID: <20070814040141.5EE75DA81F@mailserver7.hushmail.com> (raw)
On Mon, 13 Aug 2007 16:30:14 -0400 Jiri Slaby <jirislaby@gmail.com>
wrote:
>why dri-devel@lists.sourceforge.net?
>
David Airlie was listed as the owner on several of the files and in
maintainers for "DRM", which was my best to: guess for
/drivers/char/drm (which was patch 3 in this series).
If there was a better list, or just to linux-kernel, please let me
know as tracking down the 'right' list for these kernel-janitor
kind of tasks can be tricky....
---------------------------------------
Scott Thompson / postfail@hushmail.com
---------------------------------------
next prev parent reply other threads:[~2007-08-14 4:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 4:05 [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode check Scott Thompson
2007-08-13 4:05 ` Scott Thompson
2007-08-13 10:42 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode Alan Cox
2007-08-13 10:42 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode check Alan Cox
2007-08-13 12:50 ` Scott Thompson
2007-08-13 12:50 ` Scott Thompson
2007-08-13 13:21 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode Alan Cox
2007-08-13 13:21 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode check Alan Cox
2007-08-13 20:30 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode Jiri Slaby
2007-08-13 20:30 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode check Jiri Slaby
2007-08-14 4:01 ` Scott Thompson [this message]
2007-08-14 4:01 ` Scott Thompson
2007-08-15 19:38 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode Jiri Slaby
2007-08-15 19:38 ` [PATCH 4 of 5 ] /drivers/char/rio ioremap balancing/ returncode check Jiri Slaby
2007-08-15 19:52 ` Scott Thompson
2007-08-15 19:52 ` Scott Thompson
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=20070814040141.5EE75DA81F@mailserver7.hushmail.com \
--to=postfail@hushmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jirislaby@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.