From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] epca iomem annotations + several missing readw()
Date: Thu, 15 Sep 2005 23:27:30 +0100 [thread overview]
Message-ID: <20050915232730.D26124@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050915221914.GD19626@ftp.linux.org.uk>; from viro@ftp.linux.org.uk on Thu, Sep 15, 2005 at 11:19:14PM +0100
On Thu, Sep 15, 2005 at 11:19:14PM +0100, Al Viro wrote:
> On Thu, Sep 15, 2005 at 11:10:14PM +0100, Russell King wrote:
> > On Thu, Sep 15, 2005 at 08:27:04PM +0100, Al Viro wrote:
> > > [originally sent to Alan, he had no problems with it]
> > > * iomem pointers marked as such
> > > * several direct dereferencings of such pointers replaced with
> > > read[bw]().
> > > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> >
> > Thanks for copying me, but I have no interest in any serial driver
> > which doesn't use the serial core interface.
> >
> > I don't want to act as "person to review any change just because the
> > driver says serial" - that's not the role I decided to get involved
> > with.
>
> Hey, seeing the intensity of your complaints about _not_ being Cc'd...
> Better safe than serial maintainer ;-)
My feelings as well when I get random serial bugs in bugzilla for drivers
I have zero clue about and no one to assign them to. 8/
> OK, so what stuff do you want to be Cc'd on? My current approximation
> would be arch/arm/*, include/asm-arm/*,drivers/serial/*,include/linux/serial*.
> Well, and any changes of tty interfaces, if I ever get involved in such...
> Any additions/removals?
Broadly, it's:
arch/arm/*
drivers/*/arm
drivers/mfd/* (this fits at the moment, but whether it will in
the future depends what else appears there.)
drivers/mmc/*
drivers/serial* (though only the drivers in there actually using
serial_core - unfortunately some non-serial_core
drivers appear to have been placed in there.)
include/asm-arm/*
include/linux/8250*
include/linux/serial*
fs/adfs/*
but there are various drivers authored by myself which I'd obviously be
interested in CC'ed.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-09-15 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 19:27 [PATCH] epca iomem annotations + several missing readw() Al Viro
2005-09-15 21:23 ` Linus Torvalds
2005-09-15 21:38 ` Al Viro
2005-09-15 21:53 ` Al Viro
2005-09-15 22:10 ` Russell King
2005-09-15 22:19 ` Al Viro
2005-09-15 22:27 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 19:23 viro
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=20050915232730.D26124@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=viro@ftp.linux.org.uk \
/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