From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: bluez-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
caglar@pardus.org.tr, bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] [PATCH 14/14] net/bluetooth/hci_core.c: Use time_* macros
Date: Sun, 17 Feb 2008 23:25:28 -0800 (PST) [thread overview]
Message-ID: <20080217.232528.161307877.davem@davemloft.net> (raw)
In-Reply-To: <1203005031.7664.474.camel@violet>
From: Marcel Holtmann <marcel@holtmann.org>
Date: Thu, 14 Feb 2008 17:03:51 +0100
> since this is full serious of patches, I am not sure if it should go via
> the subsystem maintainers or better applied as whole. In case of Linus
> or Andrew decide to take them all at once and push them, this on is
> acked by me.
I'll take care of it.
> Acked-by: Marcel Holtmann <marcel@holtmann.org>
Thanks.
next prev parent reply other threads:[~2008-02-18 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 15:36 [Bluez-devel] [PATCH 14/14] net/bluetooth/hci_core.c: Use time_* macros S.Çağlar Onur
2008-02-14 16:03 ` Marcel Holtmann
2008-02-18 7:25 ` David Miller [this message]
2008-02-18 7:25 ` David Miller
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=20080217.232528.161307877.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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