linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Patchwork <patchwork@linuxtv.org>,
	sakari.ailus@iki.fi, laurent.pinchart@ideasonboard.com,
	linux-media@vger.kernel.org, mchehab@kernel.org,
	pali.rohar@gmail.com, sre@kernel.org,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
	patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com
Subject: Re: patchwork: on whose behalf is it working? was Re: [linux-media] Patch notification: 3 patches updated
Date: Thu, 22 Jun 2017 21:43:06 +0200	[thread overview]
Message-ID: <20170622194306.GA25853@amd> (raw)
In-Reply-To: <20170622123504.0015c78b@vento.lan>

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]

Hi!

> > > The following patches (submitted by you) have been updated in patchwork:
> > > 
> > >  * linux-media: [RFC,07/13] v4l2: device_register_subdev_nodes: allow calling multiple times
> > >      - http://patchwork.linuxtv.org/patch/39403/
> > >      - for: Linux Media kernel patches
> > >     was: New
> > >     now: Accepted  
> > 
> > Dear patchwork, I'm not sure on who's behalf you are mailing me. (And
> > that would be really nice to fix.)
> 
> Sorry, but patchwork is not smart enough to read and reply 
> e-mails yet :-) It is just a dumb robot.

Well, fortunately he's got human helpers :-).

> > If you are writing on Sakari's behalf, all is well.
> 
> > If you are writing on someone else's behalf, you may tell that
> > someone to coordinate with Sakari, because he likely has it in his
> > tree already.
> 
> From the delatate to: field, it seems that Sakari was the one
> that did the change...

Aha, thanks for the pointer.

> However, patchwork is also dumb enough to not store any info
> about who changed a status (or even to log it)...

Hopefully, patchwork will get smarter one day...

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2017-06-22 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170622150601.4956.51414@www.linuxtv.org>
2017-06-22 15:19 ` patchwork: on whose behalf is it working? was Re: [linux-media] Patch notification: 3 patches updated Pavel Machek
2017-06-22 15:34   ` Sakari Ailus
2017-06-22 15:35   ` Mauro Carvalho Chehab
2017-06-22 19:43     ` Pavel Machek [this message]

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=20170622194306.GA25853@amd \
    --to=pavel@ucw.cz \
    --cc=aaro.koskinen@iki.fi \
    --cc=abcloriens@gmail.com \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=pali.rohar@gmail.com \
    --cc=patchwork@linuxtv.org \
    --cc=patrikbachan@gmail.com \
    --cc=sakari.ailus@iki.fi \
    --cc=serge@hallyn.com \
    --cc=sre@kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).