From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch 1/2] ath6kl: change || to &&
Date: Mon, 23 Apr 2012 11:37:11 +0000 [thread overview]
Message-ID: <4F953EE7.9000006@qca.qualcomm.com> (raw)
In-Reply-To: <20120420064328.GC22649@elgon.mountain>
On 04/20/2012 09:43 AM, Dan Carpenter wrote:
> The original conditions are always true. I think && was intended here,
> but I don't have the hardware to test. Could you take a look?
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Thanks, both patches applied to ath6kl.git.
Kalle
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: Re: [patch 1/2] ath6kl: change || to &&
Date: Mon, 23 Apr 2012 14:37:11 +0300 [thread overview]
Message-ID: <4F953EE7.9000006@qca.qualcomm.com> (raw)
In-Reply-To: <20120420064328.GC22649@elgon.mountain>
On 04/20/2012 09:43 AM, Dan Carpenter wrote:
> The original conditions are always true. I think && was intended here,
> but I don't have the hardware to test. Could you take a look?
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Thanks, both patches applied to ath6kl.git.
Kalle
next prev parent reply other threads:[~2012-04-23 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 6:43 [patch 1/2] ath6kl: change || to && Dan Carpenter
2012-04-20 6:43 ` Dan Carpenter
2012-04-20 8:37 ` Kalle Valo
2012-04-20 8:37 ` Kalle Valo
2012-04-20 8:51 ` Ng, Chilam
2012-04-23 11:37 ` Kalle Valo [this message]
2012-04-23 11:37 ` Kalle Valo
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=4F953EE7.9000006@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.