From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: manual merge of the v4l-dvb tree
Date: Mon, 30 Jun 2008 08:14:25 -0300 [thread overview]
Message-ID: <20080630081425.125ca842@gaivota> (raw)
In-Reply-To: <20080630145645.b671b13d.sfr@canb.auug.org.au>
On Mon, 30 Jun 2008 14:56:45 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Mauro,
>
> Today's linux-next merge of the v4l-dvb tree got a trivial conflict in
> drivers/media/video/videodev.c between commit
> 7fa8e6fa1519194fc0c931f40d530fb55137bad9 ("V4L/DVB (8092): videodev:
> simplify and fix standard enumeration") from Linus' tree (which is also
> in the v4l-dvb tree) and commit 561216cf5e422669b4f9e54a6157d731245feecc
> ("V4L/DVB (8103): videodev: fix/improve ioctl debugging") from the
> v4l-dvb tree.
>
> Again, I fixed it up and will carry it.
Thanks. I'll rebase my tree.
> But also my comments about a bug
> fix branch/tree apply here also.
>
Hmm... I have here two branches, one with bug fixes only and another with bug fixes
+ improvements. The last one is exported into my linux-next tree. Having just
improvements on it seems a good idea, except that, sometimes, an improvement
requires first that some bug fix patch to be applied first. Anyway, I'm seeking
for some time to change my upstream procedures to get rid of those issues.
Cheers,
Mauro
next prev parent reply other threads:[~2008-06-30 11:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 4:56 linux-next: manual merge of the v4l-dvb tree Stephen Rothwell
2008-06-30 11:14 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-13 3:00 Stephen Rothwell
2010-05-13 5:18 ` Mauro Carvalho Chehab
2010-05-13 5:59 ` Stephen Rothwell
2008-10-14 7:28 Stephen Rothwell
2008-10-27 7:16 ` Stephen Rothwell
2008-10-28 11:48 ` Mauro Carvalho Chehab
2008-10-28 12:04 ` Stephen Rothwell
2008-09-01 3:22 Stephen Rothwell
2008-09-01 3:14 Stephen Rothwell
2008-09-01 3:42 ` Stephen Rothwell
2008-09-04 4:44 ` Mauro Carvalho Chehab
2008-08-19 4:11 Stephen Rothwell
2008-08-19 5:59 ` Hans Verkuil
2008-08-19 19:55 ` Greg KH
2008-07-29 3:03 Stephen Rothwell
2008-07-04 4:45 Stephen Rothwell
2008-06-30 4:49 Stephen Rothwell
2008-06-30 4:44 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=20080630081425.125ca842@gaivota \
--to=mchehab@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox