From: Marcel Holtmann <marcel@holtmann.org>
To: ingas@codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Question about a patch set that is comprised of patches for separate git repositories
Date: Mon, 02 Aug 2010 11:45:41 -0700 [thread overview]
Message-ID: <1280774741.12579.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1c6058affcf5b834ec33d0cd2bf43c61.squirrel@www.codeaurora.org>
Hi Inga,
> I am planning on submitting a patch set for hcidump that allows parsing of
> AMP related HCI commands and events. While the modification of parsing
> code is constrained to bluez-hcidump git repository, the code relies on
> changes to hci.h file that resides in bluez git repository. Basically, I
> had to create new structures and defines for OCFs and attributes and hci.h
> seemed like a logical place to do that. However, nothing else in bluez
> subdirectory is referring those new structs and constants. So the question
> is: do I have 2 separate submissions: one for bluez and the other for
> hcidump noting that hcidump depends on the patch for hci.h in bluez, or do
> I somehow generate a combined patch set?
send the patch for hci.h first. Then we see. The LE additions took like
a few rounds of review. So we do these first.
Regards
Marcel
prev parent reply other threads:[~2010-08-02 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 18:19 Question about a patch set that is comprised of patches for separate git repositories ingas
2010-08-02 18:45 ` Marcel Holtmann [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=1280774741.12579.23.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=ingas@codeaurora.org \
--cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).