All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 8
Date: Thu, 8 Nov 2012 23:52:52 +0100	[thread overview]
Message-ID: <20121108235252.10aa2d4a@gaivota.chehab> (raw)
In-Reply-To: <CA+icZUVSZSXr+DiJmqfxjGmGn+DojXRH8MkdLjbgapGdi6gXdg@mail.gmail.com>

Em Thu, 8 Nov 2012 10:10:29 +0100
Sedat Dilek <sedat.dilek@gmail.com> escreveu:

> On Thu, Nov 8, 2012 at 5:49 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi all,
> >
> > Changes since 20121107:
> >
> [...]
> >
> > The v4l-dvb tree still has its build failure so I used the version from
> > next-20121026.
> >
> 
> Hi,
> 
> I am just wondering why this v4l-dvb issues are still present...
> ...since 26-Oct-2012...
> ...Maintainer on holidays :-)?

I wish I had it ;)

> I know most Linux kernel people are visting Barcelona this week.

Well, not visiting. Working from here... and the network at the hotel sucks. 

Regards,
Mauro

  reply	other threads:[~2012-11-08 22:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  4:49 linux-next: Tree for Nov 8 Stephen Rothwell
2012-11-08  4:49 ` Stephen Rothwell
2012-11-08  9:10 ` Sedat Dilek
2012-11-08 22:52   ` Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08  4:48 Stephen Rothwell
2022-11-08  6:18 Stephen Rothwell
2021-11-08  3:51 Stephen Rothwell
2019-11-08  6:26 Stephen Rothwell
2018-11-08  4:10 Stephen Rothwell
2017-11-08  6:59 Stephen Rothwell
2016-11-08  7:38 Stephen Rothwell
2013-11-08  8:47 Stephen Rothwell
2013-11-08  8:47 ` Stephen Rothwell
2011-11-08  3:48 Stephen Rothwell

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=20121108235252.10aa2d4a@gaivota.chehab \
    --to=mchehab@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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.