All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Alexey Klimov <klimov.linux@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org,
	Douglas Schilling Landgraf <dougsland@gmail.com>
Subject: Re: linux-next: usb tree build failure
Date: Tue, 14 Oct 2008 15:26:55 -0200	[thread overview]
Message-ID: <20081014152655.0d89f02b@pedra.chehab.org> (raw)
In-Reply-To: <208cbae30810141041j2133d5a6s92d61fd5ea40fd9f@mail.gmail.com>

Hi Alexey,

The V4L/DVB and USB conflicts on linux-next are due to the merge of my tree
upstream, plus the conflict between Greg's original patch and the one on my
tree that were already merged.

No action is required from your side. It is just a matter of me and Greg to
update our trees.

Cheers,
Mauro

It it just a matter of me updating my linux-next tree.


On Tue, 14 Oct 2008 21:41:52 +0400
"Alexey Klimov" <klimov.linux@gmail.com> wrote:

> Hello, all
> Sorry, bother you all again.
> Here is the patch that removes info() and err()-statements in
> drivers/media/radio/radio-mr800.c
> Also, in previous letter i sent you patch that removes
> warn()-statements from there.
> 
> May be it can help current situation.


-- 

Cheers,
Mauro

  reply	other threads:[~2008-10-14 18:27 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  4:08 linux-next: usb tree build failure Stephen Rothwell
2008-10-14  5:51 ` Alexey Klimov
2008-10-14 17:41   ` Alexey Klimov
2008-10-14 17:26     ` Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-02  6:10 Stephen Rothwell
2010-02-02 13:53 ` Greg KH
2010-02-02 22:33   ` Stephen Rothwell
2009-08-19  8:34 Stephen Rothwell
2009-08-19 13:52 ` Greg KH
2009-08-19 23:45   ` Greg KH
2009-08-19 23:58     ` Stephen Rothwell
2009-04-29  7:17 Stephen Rothwell
2009-04-29 14:15 ` Greg KH
2009-04-29 15:00   ` Stephen Rothwell
2009-04-29 15:16     ` Greg KH
2009-04-29 15:18 ` Randy Dunlap
2009-04-29 15:37   ` Greg KH
2009-04-29 15:44     ` Randy Dunlap
2009-04-29 17:44       ` Greg KH
2009-04-29 17:53         ` Randy Dunlap
2009-04-30 16:13           ` Greg KH
2009-04-30 16:27             ` Randy Dunlap
2008-12-22  0:33 Stephen Rothwell
2008-12-22  1:31 ` Greg KH
2008-12-22  2:42   ` Stephen Rothwell
2008-12-22  6:45     ` Sam Ravnborg
2008-12-22 17:26       ` Inaky Perez-Gonzalez
2008-12-22 17:53         ` Sam Ravnborg
2008-12-22 23:37           ` Inaky Perez-Gonzalez
2008-12-23  4:31             ` Greg KH
2008-12-23  4:30           ` Greg KH
2008-12-23  4:31         ` Greg KH
2008-12-23 10:26           ` Inaky Perez-Gonzalez
2008-12-23 17:17             ` Greg KH
2008-12-24  1:07               ` Inaky Perez-Gonzalez
2009-01-05  4:34                 ` Greg KH
2009-01-05  5:55                   ` Stephen Rothwell
2008-12-29  3:55 ` Stephen Rothwell
2009-01-02  7:27   ` Greg KH
2009-01-03  4:33     ` Stephen Rothwell
2008-11-03  0:36 Stephen Rothwell
2008-11-05  4:47 ` Greg KH
2008-11-05 18:19   ` Mauro Carvalho Chehab
2008-10-14  3:59 Stephen Rothwell
2008-10-14  8:24 ` Dmitry
2008-10-14 15:42   ` Dmitry
2008-10-16 16:05 ` Greg KH
2008-10-16 17:27   ` Dmitry Baryshkov
2008-10-16 21:36   ` Dmitry Baryshkov
2008-10-17  0:26     ` Stephen Rothwell
2008-10-17  0:41       ` Dmitry
2008-10-20 18:45         ` Greg KH
2008-08-13  6:37 Stephen Rothwell
2008-08-13  7:33 ` Stephen Rothwell
2008-08-13 14:23   ` Stephen Rothwell
2008-08-14  6:28     ` Stephen Rothwell
2008-08-14  6:54       ` Stephen Rothwell
2008-08-14 12:25         ` Greg KH
2008-08-15  0:16           ` Stephen Rothwell
2008-07-18  1:31 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=20081014152655.0d89f02b@pedra.chehab.org \
    --to=mchehab@redhat.com \
    --cc=dougsland@gmail.com \
    --cc=greg@kroah.com \
    --cc=klimov.linux@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --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.