From: s.hauer@pengutronix.de (Sascha linux-arm)
To: linux-arm-kernel@lists.infradead.org
Subject: When to send patches?
Date: Wed, 10 Feb 2010 10:47:22 +0100 [thread overview]
Message-ID: <20100210094722.GL17643@pengutronix.de> (raw)
In-Reply-To: <1265758817.2545.123.camel@realization>
Hi Alberto,
On Wed, Feb 10, 2010 at 12:40:17AM +0100, Alberto Panizzo wrote:
> Hi Sascha!
> I have a question: I have to push my work on mach-mx31_3ds machine
> but the entire work need some drivers that are present now in linux-next
> but not in mxc-master.. I have to wait the next merge window or I can push
> the complete mx31_3ds sequence to you adding (or referencing) the dependencies?
Experience showed that compile breakages even temporary are a pain. You
have two possibilities: Either ifdef the code which is causes the
breakage with #ifdef MXC_KEYPAD (or whatever the correct symbol is) so
that the ifdef automaticalle comes true when the driver is there or
just wait until the driver code is merged. So far Russell didn't
complain when the board code for new drivers is merged in -rc1 time. I
prefer the second solution. Just give me a ping when the drivers hit
mainline.
Regards,
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2010-02-10 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 23:40 When to send patches? Alberto Panizzo
2010-02-10 9:47 ` Sascha linux-arm [this message]
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=20100210094722.GL17643@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).