From: chripell@gmail.com (christian pellegrin)
To: linux-arm-kernel@lists.infradead.org
Subject: misc brokenness in v2.6.34-rc2 s3c24xx
Date: Fri, 26 Mar 2010 09:54:36 +0100 [thread overview]
Message-ID: <cabda6421003260154u6a1ef6e5ia5f04f5e9cce77db@mail.gmail.com> (raw)
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.
--
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."
next reply other threads:[~2010-03-26 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 8:54 christian pellegrin [this message]
2010-03-29 19:39 ` misc brokenness in v2.6.34-rc2 s3c24xx Ben Dooks
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=cabda6421003260154u6a1ef6e5ia5f04f5e9cce77db@mail.gmail.com \
--to=chripell@gmail.com \
--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).