From: Tony Lindgren <tony@atomide.com>
To: Ameya Palande <ameya.palande@nokia.com>
Cc: omar.ramirez@ti.com, linux-omap@vger.kernel.org,
Contreras Felipe <felipe.contreras@nokia.com>,
nm@ti.com
Subject: Re: dspbridge patches in patchwork
Date: Wed, 3 Feb 2010 09:08:16 -0800 [thread overview]
Message-ID: <20100203170815.GC22747@atomide.com> (raw)
In-Reply-To: <20100203170314.GB22747@atomide.com>
* Tony Lindgren <tony@atomide.com> [100203 09:00]:
> * Ameya Palande <ameya.palande@nokia.com> [100203 04:24]:
> > Hi Tony,
> >
> > As more and more people start contributing to dspbridge code (as we have
> > seen recently) tracking patches is becoming difficult.
> >
> > Is it possible to delegate dspbridge patches to dspbridge maintainer in
> > patchwork?
>
> Yeh sure. All it takes is registering a user for pw.k.o and selecting
> linux-omap as the project.
>
> Then I need send an email with the pw.k.o user name to allow changing
> the omap patch status.
If you just want to follow the dspbridge patches, you can configure
your pwclient:
$ cat /home/tmlind/.pwclientrc
# Sample .pwclientrc file for the linux-omap project,
# running on patchwork.kernel.org.
#
# Save this file to ~/.pwclientrc
#
[base]
url: http://patchwork.kernel.org/xmlrpc/
project: linux-omap
# Adding authentication parameters will allow you to use the 'update'
# command on patches that you are allowed to edit.
# [auth]
# username: yourusername
# password: yourpassword
Then to see all the dspbridge patches, just do:
$ pwclient search dspbridge
ID State Name
-- ----- ----
6777 Not Applicable [1/3] DSPBRIDGE Offmode and DVFS Support
6778 Not Applicable [2/3] DSPBRIDGE DVFS and OFF mode support with OPP2
6814 Not Applicable [1/1] DSPBRIDGE Fix condition statement for Global Flush
...
Regards,
Tony
next prev parent reply other threads:[~2010-02-03 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 12:26 dspbridge patches in patchwork Ameya Palande
2010-02-03 17:03 ` Tony Lindgren
2010-02-03 17:08 ` Tony Lindgren [this message]
2010-02-03 17:27 ` Ameya Palande
2010-02-03 17:29 ` Ameya Palande
2010-02-03 18:17 ` Omar Ramirez Luna
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=20100203170815.GC22747@atomide.com \
--to=tony@atomide.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=omar.ramirez@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox