From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: "Jasmin J." <jasmin@anw.at>
Cc: rjkm@metzlerbros.de, linux-media@vger.kernel.org,
max.kellermann@gmail.com, d.scheller@gmx.net
Subject: Re: [PATCH 0/7] Add block read/write to en50221 CAM functions
Date: Wed, 7 Jun 2017 19:49:34 -0300 [thread overview]
Message-ID: <20170607194934.00576613@vento.lan> (raw)
In-Reply-To: <a8d025a0-b090-7c58-bb25-aed32111c1de@anw.at>
Em Wed, 7 Jun 2017 21:18:14 +0200
"Jasmin J." <jasmin@anw.at> escreveu:
> Hello Mauro!
>
> THX for looking into this!
>
> > Hmm... from what I understood, the original author for those patches
> > is Ralph, right?
> Yes. I re-formatted them into smaller pieces to be easier reviewed.
> The goal of this series is to make the Kernel version equal to the official
> DD version. But I wrote all of this already in the preamble of the series.
The problem with this series is that, while you're saying it at the
preamble, and the SOB on each patch seems to indicate it, the patches
themselves are tagging you as the author of the patch series, and not Ralph.
See the From: at the first line of each patch on it:
https://patchwork.linuxtv.org/patch/41193/
https://patchwork.linuxtv.org/patch/41194/
https://patchwork.linuxtv.org/patch/41196/
https://patchwork.linuxtv.org/patch/41197/
...
It should be, instead:
From: Ralph Metzler <km@metzlerbros.de>
For all patches he wrote (even if you later rebased or splitted
them).
Thanks,
Mauro
next prev parent reply other threads:[~2017-06-07 22:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 20:51 [PATCH 0/7] Add block read/write to en50221 CAM functions Jasmin J.
2017-05-07 20:51 ` [PATCH 1/7] [media] dvb-core/dvb_ca_en50221.c: State UNINITIALISED instead of INVALID Jasmin J.
2017-05-07 20:51 ` [PATCH 2/7] [media] dvb-core/dvb_ca_en50221.c: Increase timeout for link init Jasmin J.
2017-05-07 20:51 ` [PATCH 3/7] [media] dvb-core/dvb_ca_en50221.c: Add block read/write functions Jasmin J.
2017-06-24 19:16 ` Mauro Carvalho Chehab
2017-06-24 19:36 ` Jasmin J.
2017-06-24 20:03 ` Jasmin J.
2017-05-07 20:51 ` [PATCH 4/7] [staging] cxd2099/cxd2099.c/.h: Fixed buffer mode Jasmin J.
2017-05-07 20:51 ` [PATCH 5/7] [media] ddbridge/ddbridge-core.c: Set maximum cxd2099 block size to 512 Jasmin J.
2017-06-24 19:07 ` Mauro Carvalho Chehab
2017-05-07 20:51 ` [PATCH 6/7] [staging] cxd2099/cxd2099.c: Removed useless printing in cxd2099 driver Jasmin J.
2017-06-24 19:12 ` Mauro Carvalho Chehab
2017-05-07 20:51 ` [PATCH 7/7] [staging] cxd2099/cxd2099.c: Activate cxd2099 buffer mode Jasmin J.
2017-06-24 19:09 ` Mauro Carvalho Chehab
2017-06-07 15:57 ` [PATCH 0/7] Add block read/write to en50221 CAM functions Mauro Carvalho Chehab
2017-06-07 19:18 ` Jasmin J.
2017-06-07 22:49 ` Mauro Carvalho Chehab [this message]
2017-06-08 7:31 ` Jasmin J.
2017-06-08 8:44 ` Mauro Carvalho Chehab
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=20170607194934.00576613@vento.lan \
--to=mchehab@s-opensource.com \
--cc=d.scheller@gmx.net \
--cc=jasmin@anw.at \
--cc=linux-media@vger.kernel.org \
--cc=max.kellermann@gmail.com \
--cc=rjkm@metzlerbros.de \
/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.