From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dulshani Gunawardhana <dulshani.gunawardhana89@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: staging: media: Use dev_err() instead of pr_err()
Date: Sun, 17 Nov 2013 10:03:21 -0200 [thread overview]
Message-ID: <20131117100321.18ed7be8@samsung.com> (raw)
In-Reply-To: <20131115062939.GC28137@kroah.com>
Em Fri, 15 Nov 2013 15:29:39 +0900
Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:
> On Thu, Nov 14, 2013 at 11:08:14AM -0200, Mauro Carvalho Chehab wrote:
> > Hi,
> >
> > I'm not sure how this patch got applied upstream:
> >
> > commit b6ea5ef80aa7fd6f4b18ff2e4174930e8772e812
> > Author: Dulshani Gunawardhana <dulshani.gunawardhana89@gmail.com>
> > Date: Sun Oct 20 22:58:28 2013 +0530
> >
> > staging:media: Use dev_dbg() instead of pr_debug()
> >
> > Use dev_dbg() instead of pr_debug() in go7007-usb.c.
> >
> > Signed-off-by: Dulshani Gunawardhana <dulshani.gunawardhana89@gmail.com>
> > Reviewed-by: Josh Triplett <josh@joshtriplett.org>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >
> > But, from the custody chain, it seems it was not C/C to linux-media ML,
> > doesn't have the driver maintainer's ack[1] and didn't went via my tree.
>
> It came in through my tree as part of the OPW intern application
> process.
Ah, OK.
I don't mind if you apply those directly, but what makes me a little
worried is that at least the final version of the patchset should be
c/c to driver/subsystem maintainers for their review and for them to
know that the patch will be merged via some other tree, as it might
be causing conflicts with their trees.
> And yes, sorry, it's broken, I have some follow-on patches to fix this,
> but you are right, it should just be reverted for now, very sorry about
> that.
No problem.
> Do you want to do that, or should I?
I prefer if you could do it, as I'm still waiting the merge from my tree,
and I don't want to cascade another pull request before the original
pull requests get handled. In any case, they won't conflict with this,
as I don't have any patch for this driver on my tree for 3.13.
Thanks!
Mauro
next prev parent reply other threads:[~2013-11-17 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 13:08 Fw: staging: media: Use dev_err() instead of pr_err() Mauro Carvalho Chehab
2013-11-15 6:29 ` Greg Kroah-Hartman
2013-11-17 12:03 ` Mauro Carvalho Chehab [this message]
2013-11-19 0:47 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2013-11-05 20:26 Dan Carpenter
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=20131117100321.18ed7be8@samsung.com \
--to=m.chehab@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dulshani.gunawardhana89@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=josh@joshtriplett.org \
--cc=linux-media@vger.kernel.org \
/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.