From: Quentin Lambert <lambert.quentin@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Shigekatsu Tateno <shigekatsu.tateno@atmel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: ozwpan: Move code from success handling to error handling
Date: Tue, 10 Feb 2015 11:08:14 +0000 [thread overview]
Message-ID: <54D9E69E.9030400@gmail.com> (raw)
In-Reply-To: <20150210110441.GH5206@mwanda>
On 10/02/2015 12:04, Dan Carpenter wrote:
> On Tue, Feb 10, 2015 at 11:42:08AM +0100, Quentin Lambert wrote:
>> The original version was success handling rather than error handling,
>> therefore this patch reduces nesting.
>>
>> Signed-off-by: Quentin Lambert <lambert.quentin@gmail.com>
> Fantastic. :) Thanks!
>
> regards,
> dan carpenter
>
I am working on a second version to highlight the dependency with
the previous patch.
I don't know where the best place to signal it is though.
Should I specify it in the comment section linking the patch
via lkml mailing list?
WARNING: multiple messages have this Message-ID (diff)
From: Quentin Lambert <lambert.quentin@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Shigekatsu Tateno <shigekatsu.tateno@atmel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: ozwpan: Move code from success handling to error handling
Date: Tue, 10 Feb 2015 12:08:14 +0100 [thread overview]
Message-ID: <54D9E69E.9030400@gmail.com> (raw)
In-Reply-To: <20150210110441.GH5206@mwanda>
On 10/02/2015 12:04, Dan Carpenter wrote:
> On Tue, Feb 10, 2015 at 11:42:08AM +0100, Quentin Lambert wrote:
>> The original version was success handling rather than error handling,
>> therefore this patch reduces nesting.
>>
>> Signed-off-by: Quentin Lambert <lambert.quentin@gmail.com>
> Fantastic. :) Thanks!
>
> regards,
> dan carpenter
>
I am working on a second version to highlight the dependency with
the previous patch.
I don't know where the best place to signal it is though.
Should I specify it in the comment section linking the patch
via lkml mailing list?
next prev parent reply other threads:[~2015-02-10 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 10:42 [PATCH 1/1] staging: ozwpan: Move code from success handling to error handling Quentin Lambert
2015-02-10 10:42 ` Quentin Lambert
2015-02-10 11:04 ` Dan Carpenter
2015-02-10 11:04 ` Dan Carpenter
2015-02-10 11:08 ` Quentin Lambert [this message]
2015-02-10 11:08 ` Quentin Lambert
2015-02-10 11:15 ` Dan Carpenter
2015-02-10 11:15 ` Dan Carpenter
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=54D9E69E.9030400@gmail.com \
--to=lambert.quentin@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shigekatsu.tateno@atmel.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.