From: Johan Hedberg <johan.hedberg@gmail.com>
To: jaganath.k@samsung.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH obexd 1/2] Fix incorrect transfer path id during request authorization
Date: Wed, 11 Jan 2012 16:45:10 +0200 [thread overview]
Message-ID: <20120111144510.GA31139@x220> (raw)
In-Reply-To: <1326292215-17824-1-git-send-email-jaganath.k@samsung.com>
Hi Jaganath,
On Wed, Jan 11, 2012, jaganath.k@samsung.com wrote:
> From: jaganath.k <jaganath.k@samsung.com>
>
> Transfer is registered with id as cid, but authorize method
> is called with id as pointer to obex session structure
> ---
> src/manager.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Both of these patches look fine to me, but you need to fix your git
author name. Once you've done that please resend the patches.
I also noticed that I've by mistake already applied another patch from
you in December with the same bogus author name, so you'll end up
getting your own entry in our infamous .mailmap file.
Johan
next prev parent reply other threads:[~2012-01-11 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 14:30 [PATCH obexd 1/2] Fix incorrect transfer path id during request authorization jaganath.k
2012-01-11 14:45 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-11 15:03 Jaganath Kanakkassery
2012-01-11 15:08 ` 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=20120111144510.GA31139@x220 \
--to=johan.hedberg@gmail.com \
--cc=jaganath.k@samsung.com \
--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).