From: Nishanth Menon <menon.nishanth@gmail.com>
To: Ionut Nicu <ionut.nicu@gmail.com>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Fernando Guzman Lugo <x0095840@ti.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
linux-omap <linux-omap@vger.kernel.org>,
Ionut Nicu <ionut.nicu@mindbit.ro>
Subject: Re: [PATCH v3 1/3] staging: tidspbridge: fix mgr_enum_node_info
Date: Fri, 05 Nov 2010 12:39:13 -0400 [thread overview]
Message-ID: <4CD43331.7010705@gmail.com> (raw)
In-Reply-To: <1288974674-24330-2-git-send-email-ionut.nicu@mindbit.ro>
Ionut Nicu wrote, on 11/05/2010 12:31 PM:
> The current code was always returning a non-zero status value
> to userspace applications when this ioctl was called.
>
> The error code was ENODATA, which isn't actually an error,
> it's always returned by dcd_enumerate_object() when it hits the
> end of list.
>
> Signed-off-by: Felipe Contreras<felipe.contreras@gmail.com>
please try this as well:
a) git rebase -i master (to rebase from master if your branch is off that)
b) change this commit to edit
c) git commit --amend --author "Felipe Contreras
<felipe.contreras@gmail.com>"
to change the authorship
d) git rebase --continue
OR
edit the patch Manually and change:
From: Ionut Nicu <ionut.nicu@gmail.com>
to
From: Felipe Contreras <felipe.contreras@gmail.com>
The From shows the authorship, that way, when you do a git send email,
the proper acknowledgements are done :)
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-11-05 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 16:31 [PATCH v3 0/3] staging: tidspbridge: bugfixes Ionut Nicu
2010-11-05 16:31 ` [PATCH v3 1/3] staging: tidspbridge: fix mgr_enum_node_info Ionut Nicu
2010-11-05 16:39 ` Nishanth Menon [this message]
2010-11-05 16:31 ` [PATCH v3 2/3] staging: tidspbridge: mgr_enum_node_info cleanup Ionut Nicu
2010-11-05 16:31 ` [PATCH v3 3/3] staging: tidspbridge: fix kernel oops in bridge_io_get_proc_load Ionut Nicu
2010-12-06 8:56 ` [PATCH v3 0/3] staging: tidspbridge: bugfixes Ramirez Luna, Omar
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=4CD43331.7010705@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=greg@kroah.com \
--cc=ionut.nicu@gmail.com \
--cc=ionut.nicu@mindbit.ro \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--cc=x0095840@ti.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.