From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: New s3c2442 machine
Date: Wed, 24 Feb 2010 13:51:09 +0200 [thread overview]
Message-ID: <201002241351.25377.anarsoul@gmail.com> (raw)
In-Reply-To: <20100224113722.GD9018@sirena.org.uk>
? ????????? ?? 24 ??????? 2010 13:37:23 ????? Mark Brown ???????:
> In general (not particularly just for this) you're better off working
> with -next for things other than bug fixes since that's where any new
> code will be applied - except for during the merge window Linus' tree
> is always in the process of stabailisation with new development going
> on in -next.
Ok, thanks for response!
Regards
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100224/178ef49a/attachment-0001.sig>
next prev parent reply other threads:[~2010-02-24 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 11:18 New s3c2442 machine Vasily Khoruzhick
2010-02-24 11:37 ` Mark Brown
2010-02-24 11:51 ` Vasily Khoruzhick [this message]
2010-02-24 11:52 ` Ben Dooks
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=201002241351.25377.anarsoul@gmail.com \
--to=anarsoul@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.