From: Vojtech Pavlik <vojtech@suse.cz>
To: Adrian Bunk <bunk@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
clemens@ladisch.de, venkatesh.pallipadi@intel.com,
bob.picco@hp.com, Jeff Garzik <jeff@garzik.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC: 2.6 patch] MAINTAINERS: remove HPET entries
Date: Tue, 22 Apr 2008 01:26:49 +0200 [thread overview]
Message-ID: <20080421232649.GA3717@suse.cz> (raw)
In-Reply-To: <20080421213141.GG2633@cs181133002.pp.htv.fi>
On Tue, Apr 22, 2008 at 12:31:41AM +0300, Adrian Bunk wrote:
> On Fri, Apr 04, 2008 at 11:39:44PM +0200, Thomas Gleixner wrote:
> > On Fri, 4 Apr 2008, Jeff Garzik wrote:
> > > Thomas Gleixner wrote:
> > > > 1) drivers/char/hpet.c
> > > > include/linux/hpet.h
> > > >
> > > > due to the revert of the HPET irq assignemt, which was only affects x86.
> > >
> > >
> > > Related to this... check out jgarzik/misc-2.6.git#irq-cleanups and
> > > #irq-remove for my set of patches that remove the 'irq' argument from all irq
> > > handlers.
> > >
> > > I have a couple cleanup patches for HPET that should go in prior to the big
> > > "remove irq argument" massive change (even if people don't want to remove the
> > > 'irq' argument ultimately, the cleanup is still useful)
> > >
> > > Who is the HPET maintainer these days, if anyone?
> >
> > Dunno. It usually ends up in one of my git sinks :(
>
> So what about the patch below to avoid patches ending up at the wrong
> people?
Sure, go ahead, now that there is no x86-64 arch, my entry doesn't even
make sense.
> We had 4 different MAINTAINERS entries for HPET, but effectively Thomas
> currently is the maintainer.
>
> Remove these entries - the already existing entry for X86 should be
> better for handling to.
>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
Signed-off-by: Vojtech Pavlik <vojtech@suse.cz>
>
> ---
>
> MAINTAINERS | 20 --------------------
> 1 file changed, 20 deletions(-)
>
> 4e4d08631d04846823443559dce6feaab4ce46f3 diff --git a/MAINTAINERS b/MAINTAINERS
> index 45b86ab..b0c075a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1840,26 +1840,6 @@ P: Carlos Corbacho
> M: carlos@strangeworlds.co.uk
> S: Odd Fixes
>
> -HPET: High Precision Event Timers driver (hpet.c)
> -P: Clemens Ladisch
> -M: clemens@ladisch.de
> -S: Maintained
> -
> -HPET: i386
> -P: Venkatesh Pallipadi (Venki)
> -M: venkatesh.pallipadi@intel.com
> -S: Maintained
> -
> -HPET: x86_64
> -P: Vojtech Pavlik
> -M: vojtech@suse.cz
> -S: Maintained
> -
> -HPET: ACPI hpet.c
> -P: Bob Picco
> -M: bob.picco@hp.com
> -S: Maintained
> -
> HPFS FILESYSTEM
> P: Mikulas Patocka
> M: mikulas@artax.karlin.mff.cuni.cz
>
--
Vojtech Pavlik
Director SuSE Labs
prev parent reply other threads:[~2008-04-21 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 18:42 [GIT pull] x86 fixes for 2.6.25 Thomas Gleixner
2008-04-04 20:57 ` Jeff Garzik
2008-04-04 21:39 ` Thomas Gleixner
2008-04-21 21:31 ` [RFC: 2.6 patch] MAINTAINERS: remove HPET entries Adrian Bunk
2008-04-21 23:26 ` Vojtech Pavlik [this message]
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=20080421232649.GA3717@suse.cz \
--to=vojtech@suse.cz \
--cc=bob.picco@hp.com \
--cc=bunk@kernel.org \
--cc=clemens@ladisch.de \
--cc=hpa@zytor.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.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
all inboxes | Powered by JetHome®