From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Peter Senna Tschudin <peter.senna@gmail.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Jonathan Nieder <jrnieder@gmail.com>,
emilgoode@gmail.com, linux-media <linux-media@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 01/24] use IS_ENABLED() macro
Date: Thu, 24 Jan 2013 18:45:09 -0200 [thread overview]
Message-ID: <20130124184509.3a2c954f@redhat.com> (raw)
In-Reply-To: <50FE6148.1010200@redhat.com>
Em Tue, 22 Jan 2013 10:52:08 +0100
Hans de Goede <hdegoede@redhat.com> escreveu:
> Hi,
>
> On 01/21/2013 01:51 PM, Peter Senna Tschudin wrote:
> > On Mon, Jan 21, 2013 at 10:47 AM, Hans de Goede <hdegoede@redhat.com> wrote:
> >> Hi,
> >>
> >> Thanks for the patches I'll pick up 5 - 21 and add them to
> >> my tree for Mauro.
> > I have sent V2 of this patches with another subject and with fixed
> > commit message for two patches.
>
> Oh, those did not show up in my mailbox though, so I guess you
> did not send V2 to the linux-media list? Can you please re-send
> them to the linux-media list, then I'll pick up the gspca patches
> among them.
Hans,
Peter sent the version 2 of them on Jan, 19. Did you get them?
Anyway, I'll tag patches 5-21 for you as under_review status.
Regards,
Mauro
next prev parent reply other threads:[~2013-01-24 20:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 16:33 [PATCH 01/24] use IS_ENABLED() macro Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 02/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 03/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 04/24] " Peter Senna Tschudin
2013-01-22 14:20 ` Jonathan Corbet
2013-01-19 16:33 ` [PATCH 05/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 06/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 07/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 08/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 09/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 10/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 11/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 12/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 13/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 14/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 16/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 17/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 18/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 19/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 20/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 21/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 22/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 23/24] " Peter Senna Tschudin
2013-01-19 16:33 ` [PATCH 24/24] " Peter Senna Tschudin
2013-01-19 17:49 ` [PATCH 01/24] " Nikola Pajkovsky
2013-01-21 12:47 ` Hans de Goede
2013-01-21 12:51 ` Peter Senna Tschudin
2013-01-22 9:52 ` Hans de Goede
2013-01-24 20:45 ` Mauro Carvalho Chehab [this message]
2013-01-21 22:24 ` Jonathan Nieder
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=20130124184509.3a2c954f@redhat.com \
--to=mchehab@redhat.com \
--cc=emilgoode@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=hdegoede@redhat.com \
--cc=jrnieder@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=peter.senna@gmail.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).