From: Johan Hedberg <johan.hedberg@gmail.com>
To: Joao Paulo Rechi Vita <jprvita@openbossa.org>
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] time: fix byte position
Date: Thu, 19 Jul 2012 17:55:19 +0300 [thread overview]
Message-ID: <20120719145519.GA3879@x220.P-661HNU-F1> (raw)
In-Reply-To: <CAAngNMY8vwedEQdxvg2nUn0jqLy0vryPR6iz4Wd0Kwo5d1fHpw@mail.gmail.com>
Hi,
On Tue, Jul 10, 2012, Joao Paulo Rechi Vita wrote:
> On Thu, Jul 5, 2012 at 6:39 PM, Anderson Lizardo
> <anderson.lizardo@openbossa.org> wrote:
> > Hi Joao,
> >
> > On Thu, Jul 5, 2012 at 2:37 PM, João Paulo Rechi Vita
> > <jprvita@openbossa.org> wrote:
> >> The position of the "Time Zone" and "Daylight Saving Time" fields on
> >> the Local Time Information characteristic was inverted. This commit
> >> fix their position.
> >> ---
> >> time/server.c | 10 +++++-----
> >> 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > Patch looks good.
>
> Is there something preventing this patches to being merged? I see
> Gustavo is already sending the directory move patches, and this will
> probably not apply after his patches.
No particular reason why they weren't applied before the directory
restructuring. Could you please resend them to match the latest tree?
Johan
next prev parent reply other threads:[~2012-07-19 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 17:37 [PATCH BlueZ 1/2] time: fix byte position João Paulo Rechi Vita
2012-07-05 17:37 ` [PATCH BlueZ 2/2] time: fix daylight variable description João Paulo Rechi Vita
2012-07-05 17:50 ` Anderson Lizardo
2012-07-10 13:58 ` [PATCH BlueZ] " João Paulo Rechi Vita
2012-07-05 21:39 ` [PATCH BlueZ 1/2] time: fix byte position Anderson Lizardo
2012-07-10 14:03 ` Joao Paulo Rechi Vita
2012-07-19 14:55 ` Johan Hedberg [this message]
2012-07-19 17:46 ` João Paulo Rechi Vita
2012-07-23 21:33 ` Johan Hedberg
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=20120719145519.GA3879@x220.P-661HNU-F1 \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--cc=jprvita@openbossa.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