From: dwalker@fifo99.com
To: Paul Bolle <pebolle@tiscali.nl>
Cc: David Brown <davidb@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: msm: remove board file for Nexus One (ie. mahimahi)
Date: Mon, 19 May 2014 14:30:33 +0000 [thread overview]
Message-ID: <20140519143033.GA17442@fifo99.com> (raw)
In-Reply-To: <1400500408.2007.29.camel@x220>
On Mon, May 19, 2014 at 01:53:28PM +0200, Paul Bolle wrote:
> Daniel,
>
> On Thu, 2014-05-15 at 21:57 +0000, dwalker@fifo99.com wrote:
> > On Thu, May 15, 2014 at 08:10:13PM +0200, Paul Bolle wrote:
> > > This is not something I get to decide. Nevertheless, given that this
> > > file shouldn't have been merged to begin with, I'd appreciate it if some
> > > deadline could be agreed upon.
> >
> > I think I merged it actually, but there's no rules about what gets merged. How when what order, etc.
> > It's all free form.
>
> There do not seem to be formal rules. But there surely are some
> requirements for code to be added. One of the requirements is, I think,
> that it should build. This file cannot be built: it is not wired into a
> Makefile and it also includes, what appears to be, its own header file,
> but that header is not part of the tree.
The requirements are created by the maintainers.. In this case I would have expected
support for this phone much sooner, and there are in fact patches on the list to support
it which just haven't been merged yet.
> Even the most dubious of code in drivers/staging is expected to "compile
> properly"!
But mach-msm isn't staging, different rules apply there.
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: dwalker@fifo99.com (dwalker at fifo99.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: msm: remove board file for Nexus One (ie. mahimahi)
Date: Mon, 19 May 2014 14:30:33 +0000 [thread overview]
Message-ID: <20140519143033.GA17442@fifo99.com> (raw)
In-Reply-To: <1400500408.2007.29.camel@x220>
On Mon, May 19, 2014 at 01:53:28PM +0200, Paul Bolle wrote:
> Daniel,
>
> On Thu, 2014-05-15 at 21:57 +0000, dwalker at fifo99.com wrote:
> > On Thu, May 15, 2014 at 08:10:13PM +0200, Paul Bolle wrote:
> > > This is not something I get to decide. Nevertheless, given that this
> > > file shouldn't have been merged to begin with, I'd appreciate it if some
> > > deadline could be agreed upon.
> >
> > I think I merged it actually, but there's no rules about what gets merged. How when what order, etc.
> > It's all free form.
>
> There do not seem to be formal rules. But there surely are some
> requirements for code to be added. One of the requirements is, I think,
> that it should build. This file cannot be built: it is not wired into a
> Makefile and it also includes, what appears to be, its own header file,
> but that header is not part of the tree.
The requirements are created by the maintainers.. In this case I would have expected
support for this phone much sooner, and there are in fact patches on the list to support
it which just haven't been merged yet.
> Even the most dubious of code in drivers/staging is expected to "compile
> properly"!
But mach-msm isn't staging, different rules apply there.
Daniel
next prev parent reply other threads:[~2014-05-19 14:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 21:07 [PATCH] arm: msm: remove board file for Nexus One (ie. mahimahi) Paul Bolle
2014-05-14 21:07 ` Paul Bolle
2014-05-15 17:44 ` dwalker
2014-05-15 17:44 ` dwalker at fifo99.com
2014-05-15 18:10 ` Paul Bolle
2014-05-15 18:10 ` Paul Bolle
2014-05-15 21:57 ` dwalker
2014-05-15 21:57 ` dwalker at fifo99.com
2014-05-19 11:53 ` Paul Bolle
2014-05-19 11:53 ` Paul Bolle
2014-05-19 14:30 ` dwalker [this message]
2014-05-19 14:30 ` dwalker at fifo99.com
2014-05-20 6:43 ` Ivan T. Ivanov
2014-05-20 6:43 ` Ivan T. Ivanov
2014-05-29 18:29 ` Pavel Machek
2014-05-29 18:29 ` Pavel Machek
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=20140519143033.GA17442@fifo99.com \
--to=dwalker@fifo99.com \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pebolle@tiscali.nl \
/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.