On Thu, 2008-05-01 at 02:34 +0300, Adrian Bunk wrote:
quoted text
> On Wed, Apr 30, 2008 at 06:42:02PM +0100, David Woodhouse wrote:
> > Andrew Morton has been saying recently that we need an 'embedded
> > maintainer', to take responsibility for 'embedded issues' in the core
> > kernel, as well as trying to improve our relationship with those using
> > the Linux kernel for 'embedded' devices -- who have a reputation of
> > not working with us very closely; to their detriment as well as our
> > own.
> > 
> > Various people, including myself, have been doing that kind of thing
> > on and off over the years anyway, but Andrew is probably right that
> > it's worth having someone listed in the MAINTAINERS file who actually
> > considers it their responsibility, and as a point of contact for
> > people seeking advice, review, etc.
> >...
> 
> MAINTAINERS is mostly for finding the right contact for bug reports and 
> patches.
> 
> For what should I Cc you and for what should I Cc you not?

The rôle of 'embedded maintainer' is a little different to other
maintainers -- it's not about owning a certain part of the code. We need
to keep an eye on changes throughout the kernel, for how they affect
embedded systems. That's not just 'bloatwatch', but other things too --
making sure that people don't keep assuming that "all the world's a PC",
for sure, but also feature requests -- talking to those working on XIP
for S390 block devices, and trying to ensure that the infrastructure
work they do is useful for XIP from flash in embedded systems, to pick
an example from the not-so-distant past.

So I can't really give you a simple answer to the question. It's
"anything which could have implications for embedded systems which
normal people might not have thought of". But I'll continue to trawl
linux-kernel with that mindset anyway, so I wouldn't worry _too_ much.

I see the linux-embedded list being mostly useful in bringing developers
"into the fold" from companies who have largely been resistant to being
part of the community. Asking them to join linux-kernel is probably not
a good idea; I see it as a kind of targeted kernelnewbies, in one sense.

-- 
dwmw2

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/