* New s3c2442 machine
@ 2010-02-24 11:18 Vasily Khoruzhick
2010-02-24 11:37 ` Mark Brown
2010-02-24 11:52 ` Ben Dooks
0 siblings, 2 replies; 4+ messages in thread
From: Vasily Khoruzhick @ 2010-02-24 11:18 UTC (permalink / raw)
To: linux-arm-kernel
Hi, I'm going to submit patch series to add support for s3c2442-based iPAQ
rx1950 machine (once again :)). Which kernel tree should I use as base? Ben's
next-samsung branch from git.fluff.org or Linus' master branch from
git.kernel.org?
Regards
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100224/15b619b9/attachment.sig>
^ permalink raw reply [flat|nested] 4+ messages in thread
* New s3c2442 machine
2010-02-24 11:18 New s3c2442 machine Vasily Khoruzhick
@ 2010-02-24 11:37 ` Mark Brown
2010-02-24 11:51 ` Vasily Khoruzhick
2010-02-24 11:52 ` Ben Dooks
1 sibling, 1 reply; 4+ messages in thread
From: Mark Brown @ 2010-02-24 11:37 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Feb 24, 2010 at 01:18:53PM +0200, Vasily Khoruzhick wrote:
> Hi, I'm going to submit patch series to add support for s3c2442-based iPAQ
> rx1950 machine (once again :)). Which kernel tree should I use as base? Ben's
> next-samsung branch from git.fluff.org or Linus' master branch from
> git.kernel.org?
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* New s3c2442 machine
2010-02-24 11:37 ` Mark Brown
@ 2010-02-24 11:51 ` Vasily Khoruzhick
0 siblings, 0 replies; 4+ messages in thread
From: Vasily Khoruzhick @ 2010-02-24 11:51 UTC (permalink / raw)
To: linux-arm-kernel
? ????????? ?? 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>
^ permalink raw reply [flat|nested] 4+ messages in thread
* New s3c2442 machine
2010-02-24 11:18 New s3c2442 machine Vasily Khoruzhick
2010-02-24 11:37 ` Mark Brown
@ 2010-02-24 11:52 ` Ben Dooks
1 sibling, 0 replies; 4+ messages in thread
From: Ben Dooks @ 2010-02-24 11:52 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Feb 24, 2010 at 01:18:53PM +0200, Vasily Khoruzhick wrote:
> Hi, I'm going to submit patch series to add support for s3c2442-based iPAQ
> rx1950 machine (once again :)). Which kernel tree should I use as base? Ben's
> next-samsung branch from git.fluff.org or Linus' master branch from
> git.kernel.org?
you'll be better off using next-samsung, the s3c2440 and s3c2442 got
squashed together.
> Regards
> Vasily
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-02-24 11:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-24 11:18 New s3c2442 machine Vasily Khoruzhick
2010-02-24 11:37 ` Mark Brown
2010-02-24 11:51 ` Vasily Khoruzhick
2010-02-24 11:52 ` Ben Dooks
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).