From: maramaopercheseimorto@gmail.com (Alberto Panizzo)
To: linux-arm-kernel@lists.infradead.org
Subject: When to send patches?
Date: Wed, 10 Feb 2010 00:40:17 +0100 [thread overview]
Message-ID: <1265758817.2545.123.camel@realization> (raw)
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?
Best Regards!
--
Alberto!
next reply other threads:[~2010-02-09 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 23:40 Alberto Panizzo [this message]
2010-02-10 9:47 ` When to send patches? Sascha linux-arm
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=1265758817.2545.123.camel@realization \
--to=maramaopercheseimorto@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 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.