From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Jaswinder Singh <jaswinder@infradead.org>, linux-next@vger.kernel.org
Subject: linux-next: firmware tree
Date: Tue, 6 Jan 2009 18:08:24 +1100 [thread overview]
Message-ID: <20090106180824.df6ed0c7.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
Hi David,
It would be good if you could synchronise the firmware tree with Linus'
tree now that some of the commits have gone upstream. It would also be
good if the version submitted to other maintainers matched what was in
the firmware tree ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-01-06 7:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090106180824.df6ed0c7.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dwmw2@infradead.org \
--cc=jaswinder@infradead.org \
--cc=linux-next@vger.kernel.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