From: Tony Lindgren <tony@atomide.com>
To: Cory Maccarrone <darkstar6262@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Additional patches for USB support on HTC Herald?
Date: Sun, 22 Nov 2009 12:22:25 -0800 [thread overview]
Message-ID: <20091122202225.GD4860@atomide.com> (raw)
In-Reply-To: <6cb013310911221154t6e902548x3d5f212f4834692c@mail.gmail.com>
* Cory Maccarrone <darkstar6262@gmail.com> [091122 11:54]:
> Hi all,
>
> I recently submitted patches to get HTC Herald board support into the
> kernel, and they've been added to the for-next branch. Since then,
> I've managed to get USB support working for that board, so my question
> is, with the patches not yet pulled into the kernel proper, if I
> submitted an incremental patch against my previous one, is that ok?
> Or should I re-submit the whole herald board patchset with USB in?
Please submit the additional patches against the omap for-next branch,
we should still have enough time to get those in.
Regards,
Tony
prev parent reply other threads:[~2009-11-22 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 19:54 Additional patches for USB support on HTC Herald? Cory Maccarrone
2009-11-22 20:22 ` 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=20091122202225.GD4860@atomide.com \
--to=tony@atomide.com \
--cc=darkstar6262@gmail.com \
--cc=linux-omap@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