From: Grant Likely <grant.likely@linaro•org>
To: Greg KH <greg@kroah•com>, Russell King <rmk@arm•linux.org.uk>
Cc: Mauro Carvalho Chehab <mchehab@infradead•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Philipp Zabel <p.zabel@pengutronix•de>,
Sylwester Nawrocki <s.nawrocki@samsung•com>,
Laurent Pinchart <laurent.pinchart@ideasonboard•com>,
Mauro Carvalho Chehab <m.chehab@samsung•com>
Subject: Re: linux-next: manual merge of the staging tree with the v4l-dvb tree
Date: Fri, 21 Mar 2014 12:24:33 +0000 [thread overview]
Message-ID: <20140321122434.06755C40567@trevor.secretlab.ca> (raw)
In-Reply-To: <20140319153008.GC31293@kroah.com>
On Wed, 19 Mar 2014 08:30:08 -0700, Greg KH <greg@kroah•com> wrote:
> On Mon, Mar 17, 2014 at 10:27:36PM +0000, Russell King wrote:
> > However, I still find myself coming back to a fundamental question: why
> > were these bindings fine in April 2013, passed review, and were acked,
> > but not fine today. Here's the links to the emails acking their
> > introduction which Sylwester Nawrocki sent me:
> >
> > http://www.spinics.net/lists/linux-media/msg61899.html
> > http://www.spinics.net/lists/linux-media/msg62458.html
> >
> > So... *shrug*. Make of this what you will.
>
> Thanks for the details, I'll just leave my tree as-is for now, as that
> seems the simplest thing to do.
Yes, please leave it in your tree. I've caused noise and trouble than I
should, and could have handled it differently. I apologize.
g.
next prev parent reply other threads:[~2014-03-21 12:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 7:55 linux-next: manual merge of the staging tree with the v4l-dvb tree Stephen Rothwell
2014-03-17 11:01 ` Mauro Carvalho Chehab
2014-03-17 18:29 ` Greg KH
[not found] ` < 20140317162937.2ccdec83@infradead.org>
2014-03-17 19:29 ` Mauro Carvalho Chehab
2014-03-17 22:27 ` Russell King
2014-03-19 15:30 ` Greg KH
2014-03-21 12:24 ` Grant Likely [this message]
2014-03-21 14:37 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2024-10-16 3:18 Stephen Rothwell
2024-10-16 5:48 ` Greg KH
2023-02-13 2:13 Stephen Rothwell
2023-02-13 7:05 ` Greg KH
2020-03-23 4:18 Stephen Rothwell
2020-03-23 9:56 ` Greg KH
2020-03-19 3:44 Stephen Rothwell
2020-03-19 8:30 ` Greg KH
2019-04-26 6:06 Stephen Rothwell
2019-04-27 6:36 ` Greg KH
2019-05-08 1:54 ` Stephen Rothwell
2019-04-04 2:43 Stephen Rothwell
2018-12-10 5:53 Stephen Rothwell
2018-10-08 4:53 Stephen Rothwell
2018-10-08 4:47 Stephen Rothwell
2018-05-17 4:17 Stephen Rothwell
2018-05-17 7:22 ` Greg KH
2018-05-17 10:06 ` Mauro Carvalho Chehab
2018-05-26 4:45 ` Stephen Rothwell
2017-11-02 4:30 Stephen Rothwell
2017-04-11 3:32 Stephen Rothwell
2017-04-06 3:34 Stephen Rothwell
2017-04-06 18:58 ` Sean Young
2017-04-06 19:19 ` Greg KH
2017-04-06 20:39 ` Sean Young
2017-04-06 21:51 ` Stephen Rothwell
2017-02-06 4:31 Stephen Rothwell
2017-02-06 8:37 ` Greg KH
2016-03-04 5:24 Stephen Rothwell
2016-03-04 16:58 ` Greg KH
2015-05-11 5:28 Stephen Rothwell
2015-05-11 18:34 ` Greg KH
2015-03-24 5:29 Stephen Rothwell
2014-11-24 8:10 Stephen Rothwell
2014-11-24 8:09 Stephen Rothwell
2014-11-05 4:37 Stephen Rothwell
2014-11-05 4:31 Stephen Rothwell
2014-11-05 4:29 Stephen Rothwell
2014-11-06 2:19 ` Greg KH
2014-07-16 6:46 Stephen Rothwell
2014-07-16 20:52 ` Greg KH
2014-03-18 6:15 Stephen Rothwell
2011-09-27 6:10 Stephen Rothwell
2011-09-27 14:18 ` Greg KH
2011-09-27 20:14 ` Paul Gortmaker
2011-07-16 13:03 Stephen Rothwell
2011-07-17 9:15 ` Greg KH
2011-03-04 5:39 Stephen Rothwell
2011-03-04 17:14 ` Greg KH
2011-03-04 5:39 Stephen Rothwell
2011-03-04 17:14 ` Greg KH
2011-03-04 5:39 Stephen Rothwell
2011-03-04 17:13 ` Greg KH
2011-03-04 17:54 ` Mauro Carvalho Chehab
2011-03-04 21:23 ` Greg KH
2011-03-04 22:17 ` Mauro Carvalho Chehab
2011-03-04 5:38 Stephen Rothwell
2011-03-04 17:12 ` Greg KH
2011-03-04 5:38 Stephen Rothwell
2011-03-04 17:13 ` Greg KH
2011-03-04 5:38 Stephen Rothwell
2011-03-04 17:12 ` Greg KH
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=20140321122434.06755C40567@trevor.secretlab.ca \
--to=grant.likely@linaro$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=laurent.pinchart@ideasonboard$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=m.chehab@samsung$(echo .)com \
--cc=mchehab@infradead$(echo .)org \
--cc=p.zabel@pengutronix$(echo .)de \
--cc=rmk@arm$(echo .)linux.org.uk \
--cc=s.nawrocki@samsung$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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