From: Tony Lindgren <tony@atomide.com>
To: "Luís Vitório Cargnini" <lvcargnini@ieee.org>
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] MTD patch, including the latest modifications an offical upgrades for MTD
Date: Thu, 19 Oct 2006 17:05:04 +0300 [thread overview]
Message-ID: <20061019140502.GJ9983@atomide.com> (raw)
In-Reply-To: <ae36f8040609041942l93b51fapd7641d46f6c6b686@mail.gmail.com>
Hi,
* Luís Vitório Cargnini <lvcargnini@ieee.org> [060905 05:48]:
> Dear Colleagues,
> I'm submitting the latest upgrades from MTD (generated by infrared)
> to patch:
> cd to <linux_dir>
> patch -p1 < ../mtd.patch
>
> official announce:
> "...
> Gitweb can give patches between specific points in the tree. To obtain
> the full patch between Linus' official kernel tree and the current MTD
> tree, use the following URL:
> http://git.infradead.org/?p=mtd-2.6.git;a=commitdiff_plain;h=master;hp=linus
> . This produces a full patch from the branch known as 'linus ' in the
> git repository, which represents the last point at which Linus'
> official kernel tree was merged into the MTD git tree. This should
> apply correctly to the current kernel, but beware that it will not
> include changes which were already taken by Linus.
> ..."
> i merged and it are working well for me
I'd rather stick with the mainline MTD to cut down on merge issues
unless some specific bugfixes are needed for MTD to work on omap.
But it's nice to know that you can easily generate the patch for it
in case somebody needs it :)
Tony
prev parent reply other threads:[~2006-10-19 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 2:42 [PATCH] MTD patch, including the latest modifications an offical upgrades for MTD Luís Vitório Cargnini
2006-10-19 14:05 ` Tony Lindgren [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=20061019140502.GJ9983@atomide.com \
--to=tony@atomide.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=lvcargnini@ieee.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