From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-media@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [v2] [media] Use common error handling code in 20 functions
Date: Tue, 6 Mar 2018 18:08:25 +0100 [thread overview]
Message-ID: <809fdf67-70a1-0977-4008-62a3824fecd0@users.sourceforge.net> (raw)
In-Reply-To: <227d2d7c-5aee-1190-1624-26596a048d9c@users.sourceforge.net>
I got the following notification.
- http://patchwork.linuxtv.org/patch/47270/
- for: Linux Media kernel patches
was: New
now: Rejected
Would you like to clarify still any other variant for this change proposal?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-media@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [v2] [media] Use common error handling code in 20 functions
Date: Tue, 06 Mar 2018 17:08:25 +0000 [thread overview]
Message-ID: <809fdf67-70a1-0977-4008-62a3824fecd0@users.sourceforge.net> (raw)
In-Reply-To: <227d2d7c-5aee-1190-1624-26596a048d9c@users.sourceforge.net>
I got the following notification.
- http://patchwork.linuxtv.org/patch/47270/
- for: Linux Media kernel patches
was: New
now: Rejected
Would you like to clarify still any other variant for this change proposal?
Regards,
Markus
next prev parent reply other threads:[~2018-03-06 17:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 18:11 [PATCH v2] [media] Use common error handling code in 20 functions SF Markus Elfring
2018-02-19 18:11 ` SF Markus Elfring
2018-02-19 18:37 ` Laurent Pinchart
2018-02-19 18:37 ` Laurent Pinchart
2018-02-28 8:45 ` [v2] " SF Markus Elfring
2018-02-28 8:45 ` SF Markus Elfring
2018-02-28 8:59 ` Laurent Pinchart
2018-02-28 8:59 ` Laurent Pinchart
2018-02-20 8:07 ` [PATCH v2] " Todor Tomov
2018-02-20 8:07 ` Todor Tomov
2018-03-06 17:08 ` SF Markus Elfring [this message]
2018-03-06 17:08 ` [v2] " SF Markus Elfring
2018-03-09 20:10 ` [PATCH v3] [media] Use common error handling code in 19 functions SF Markus Elfring
2018-03-09 20:10 ` SF Markus Elfring
2018-03-12 9:30 ` Todor Tomov
2018-03-12 9:30 ` Todor Tomov
2018-05-04 16:08 ` [v3] " SF Markus Elfring
2018-05-04 16:08 ` SF Markus Elfring
2018-05-04 17:50 ` Mauro Carvalho Chehab
2018-05-04 17:50 ` Mauro Carvalho Chehab
2018-05-05 7:53 ` SF Markus Elfring
2018-05-05 7:53 ` SF Markus Elfring
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=809fdf67-70a1-0977-4008-62a3824fecd0@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=akpm@linux-foundation.org \
--cc=hans.verkuil@cisco.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/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.