From: Ben Dooks <ben-linux@fluff.org>
To: christian pellegrin <chripell@gmail.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: misc brokenness in v2.6.34-rc2 s3c24xx
Date: Mon, 29 Mar 2010 20:39:21 +0100 [thread overview]
Message-ID: <20100329193921.GH31126@trinity.fluff.org> (raw)
In-Reply-To: <cabda6421003260154u6a1ef6e5ia5f04f5e9cce77db@mail.gmail.com>
On Fri, Mar 26, 2010 at 09:54:36AM +0100, christian pellegrin wrote:
> Hi,
>
> some time ago I sent a couple of patches that fix some bugs in s3c24xx
> code (nand clock stop, suspend/resume gpio state preservation). I
> started to work on 2.6.34-rcX and noticed they didn't make it to the
> repository. Was there something wrong with the patches or with the
> procedure for submitting them? Where can I monitor if the patches are
> waiting in someone queue? Thanks.
I'll be looking at these again over the next few days.
> --
> Christian Pellegrin, see http://www.evolware.org/chri/
> "Real Programmers don't play tennis, or any other sport which requires
> you to change clothes. Mountain climbing is OK, and Real Programmers
> wear their climbing boots to work in case a mountain should suddenly
> spring up in the middle of the computer room."
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: misc brokenness in v2.6.34-rc2 s3c24xx
Date: Mon, 29 Mar 2010 20:39:21 +0100 [thread overview]
Message-ID: <20100329193921.GH31126@trinity.fluff.org> (raw)
In-Reply-To: <cabda6421003260154u6a1ef6e5ia5f04f5e9cce77db@mail.gmail.com>
On Fri, Mar 26, 2010 at 09:54:36AM +0100, christian pellegrin wrote:
> Hi,
>
> some time ago I sent a couple of patches that fix some bugs in s3c24xx
> code (nand clock stop, suspend/resume gpio state preservation). I
> started to work on 2.6.34-rcX and noticed they didn't make it to the
> repository. Was there something wrong with the patches or with the
> procedure for submitting them? Where can I monitor if the patches are
> waiting in someone queue? Thanks.
I'll be looking at these again over the next few days.
> --
> Christian Pellegrin, see http://www.evolware.org/chri/
> "Real Programmers don't play tennis, or any other sport which requires
> you to change clothes. Mountain climbing is OK, and Real Programmers
> wear their climbing boots to work in case a mountain should suddenly
> spring up in the middle of the computer room."
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-03-29 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 8:54 misc brokenness in v2.6.34-rc2 s3c24xx christian pellegrin
2010-03-26 8:54 ` christian pellegrin
2010-03-29 19:39 ` Ben Dooks [this message]
2010-03-29 19:39 ` Ben Dooks
2010-03-30 5:21 ` christian pellegrin
2010-03-30 5:21 ` christian pellegrin
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=20100329193921.GH31126@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=chripell@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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 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.