All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Greg KH <greg@kroah.com>, Alan Cox <alan@linux.intel.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] atomisp2: unify some ifdef cases caused by format changes
Date: Wed, 8 Mar 2017 13:45:36 -0300	[thread overview]
Message-ID: <20170308134536.2ceeed19@vento.lan> (raw)
In-Reply-To: <2540e923-6468-a283-26ff-9e48a4f18157@xs4all.nl>

Em Wed, 8 Mar 2017 14:55:44 +0100
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> On 08/03/17 14:45, Hans Verkuil wrote:
> > On 08/03/17 14:39, Greg KH wrote:  
> >> On Wed, Mar 08, 2017 at 01:49:23PM +0100, Hans Verkuil wrote:  
> >>> OK, so I discovered that these patches are for a driver added to linux-next
> >>> without it ever been cross-posted to linux-media.
> >>>
> >>> To be polite, I think that's rather impolite.  
> >>
> >> They were, but got rejected due to the size :(
> >>
> >> Mauro was cc:ed directly, he knew these were coming...
> >>
> >> I can take care of the cleanup patches for now, you don't have to review
> >> them if you don't want to.  
> >
> > Please do.
> >
> > For the next time if the patches are too large: at least post a message with
> > a link to a repo for people to look at. I would like to know what's going
> > on in staging/media, especially since I will do a lot of the reviewing (at
> > least if it is a V4L2 driver) when they want to move it out of staging.  
> 
> Same issue BTW with the bcm2835 driver. That too landed in staging without
> ever being posted to the linux-media mailinglist. Size is no excuse for that
> driver since it isn't that large.

This one got posted at media ML:
	https://patchwork.linuxtv.org/project/linux-media/list/?state=*&q=2835

(patches 1/6 to 6/6)

Thanks,
Mauro

      parent reply	other threads:[~2017-03-08 16:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 11:21 [PATCH] atomisp2: unify some ifdef cases caused by format changes Alan Cox
2017-03-08 12:49 ` Hans Verkuil
2017-03-08 13:39   ` Greg KH
2017-03-08 13:45     ` Hans Verkuil
2017-03-08 13:55       ` Hans Verkuil
2017-03-08 14:20         ` Greg KH
2017-03-08 14:22           ` Hans Verkuil
2017-03-08 14:32         ` Hans Verkuil
2017-03-08 16:45         ` Mauro Carvalho Chehab [this message]

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=20170308134536.2ceeed19@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=alan@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=hverkuil@xs4all.nl \
    --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.