From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Pending patches for s5pc110
Date: Fri, 11 Jun 2010 08:54:57 +0100 [thread overview]
Message-ID: <20100611075457.GZ7248@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTimnuN9h-qka3pRlmaEsR8o6IzFgl3A2YQ5Y28HJ@mail.gmail.com>
On Fri, Jun 11, 2010 at 04:07:58PM +0900, Kyungmin Park wrote:
> On Fri, Jun 11, 2010 at 3:23 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> > On Fri, Jun 11, 2010 at 02:38:56PM +0900, Kyungmin Park wrote:
> >> On Fri, Jun 11, 2010 at 2:15 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> >> > On Fri, Jun 11, 2010 at 01:25:18PM +0900, Kyungmin Park wrote:
> >> >> Hi,
> >> >>
> >> >> No comments mean it's okay then we will prepare the patches to git pull.
> >> >
> >> > No. no comments means that people either haven't had time to sort
> >> > them out or in fact ON HOLIDAY.
> >>
> >> but you usually missed our patches frequently. with this reason our
> >> patches can't merge within proper merge window.
> >
> > I belive the last set where either being posted just-before or during
> > the last merge window. We already had far too much queueud up then and
> > we where trying to ensure that the already-queued entries where processed.
>
> Not tell this case, please see the s5pc110 patches last year. last
> year we sent the s5pc110 related patches several times. but you don't
> give any opinions and can't accept without any reason.
I gave you comments, or at least Marke should have got them for the
series sent in November, then there's nothing in my mailbox since
then.
> Well it's past story, forget it.
>
> Last question.
>
> I think you share the s3c maintainer-ship with Kukjin. Can you explain
> the criteria?
Ok, here's the list:
1) SystemLSI are the best placed to see all the chips in development,
since they're the ones making them. You are only dealing with a
subset of their output (generally the S5PC100 and S5PC110) whereas
there are many more devices in the line.
2) SystemLSI have spent time talking to me about what they need to do
when maintaining a system and trying to acquire the necessary skills
for managing a port.
This does not mean that you cannot be included at a later date.
As a note, that I have left myself in the maintainers entries for the
samsung series and will re-visit this once we see how well the transfer
goes in the next kernel release or two.
--
Ben
next prev parent reply other threads:[~2010-06-11 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTil0wWSFHpwi58enMhhG7475uUmFoZG6QhRim6Xk@mail.gmail.com>
2010-06-11 4:25 ` Pending patches for s5pc110 Kyungmin Park
2010-06-11 5:15 ` Ben Dooks
2010-06-11 5:38 ` Kyungmin Park
2010-06-11 6:18 ` Kukjin Kim
2010-06-11 6:23 ` Ben Dooks
2010-06-11 7:07 ` Kyungmin Park
2010-06-11 7:54 ` Ben Dooks [this message]
2010-06-11 8:15 ` Kyungmin Park
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=20100611075457.GZ7248@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).