From: ebiederman@lnxi.com (Eric W. Biederman)
To: <linux-mtd@lists.infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Q: Pushing code to 2.4.x
Date: 29 Jan 2003 14:32:23 -0700 [thread overview]
Message-ID: <m3wuknzlp4.fsf@lnxi.com> (raw)
What is the plan for keeping the kernel and the CVS tree more or less in sync?
There are currently some large divergences, to the point there are some
chips that I can use the cfi_cmdset_0002.c from the stable 2.4.x kernel mtd tree
but not from the recent CVS tree.
In addition on the boards I support LinuxBIOS on I ensure there are kernel
mtd drivers that allow people to flash their BIOS rom. And my customers would
like to see those drivers in the stock kernel.
For the short term I can release and maintain patch where everything works,
the question is what should my long term strategy be.
A) Push to the MTD cvs repository and let David Woodhouse push to Marcelo.
B) Push to the MTD cvs repository and push directly to Marcelo.
C) Some more involved coordination of the MTD drivers.
With LinuxBIOS becoming a fully supported product I expect to continually
have more board and more little rom chips that I am making certain work.
Eric
next reply other threads:[~2003-01-29 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 21:32 Eric W. Biederman [this message]
2003-01-29 21:44 ` Q: Pushing code to 2.4.x David Woodhouse
2003-01-29 22:34 ` Eric W. Biederman
2003-01-31 14:19 ` David Woodhouse
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=m3wuknzlp4.fsf@lnxi.com \
--to=ebiederman@lnxi.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@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