linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org
Cc: Julia Lawall <julia.lawall@lip6.fr>, Jan Kara <jack@suse.cz>,
	Lorenzo Stoakes <lstoakes@gmail.com>,
	Michal Hocko <mhocko@suse.com>,
	Muralidharan Karicheri <mkaricheri@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: Adjustments for a lot of function implementations
Date: Mon, 30 Oct 2017 11:48:03 +0100	[thread overview]
Message-ID: <804550a6-1096-12f1-a0ec-1ccd6bcc191e@xs4all.nl> (raw)
In-Reply-To: <049aa1b4-6291-ec24-1ffb-77ae8d1cdb63@users.sourceforge.net>

On 10/30/2017 11:40 AM, SF Markus Elfring wrote:
>>>>> Feel free to repost, but only if you organize the patch as either fixing the same type of
>>>>> issue for a whole subdirectory (media/usb, media/pci, etc)
>>>
>>> Just for the record, while this may work for media, it won't work for all
>>> subsystems.  One will quickly get a complaint that the big patch needs to
>>> go into multiple trees.
>>
>> For the record: this only applies to drivers/media.
> 
> Interesting …
> 
> 
>> We discussed what do to with series like this during our media summit last Friday
> 
> Would you like to share any more information from this meeting?

??? I did that: either one patch per directory with the same type of change,
or one patch per driver combining all the changes for that driver.

> 
> 
>> and this was the conclusion of that.
> 
> I would appreciate further indications for a corresponding change acceptance.
> 
> I found a feedback by Mauro Carvalho Chehab more constructive.
> 
> [GIT,PULL,FOR,v4.15] Cleanup fixes
> https://patchwork.linuxtv.org/patch/43957/
> 
> “…
> This time, I was nice and I took some time doing:
> 
> 	$ quilt fold < `quilt next` && quilt delete `quilt next`
> …”

Yes, and you were told not to do it like that again.

Regards,

	Hans

  reply	other threads:[~2017-10-30 10:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 10:20 [PATCH 0/6] [media] omap_vout: Adjustments for three function implementations SF Markus Elfring
2017-09-24 10:22 ` [PATCH 1/6] [media] omap_vout: Delete an error message for a failed memory allocation in omap_vout_create_video_devices() SF Markus Elfring
2017-09-24 10:35   ` Joe Perches
2017-09-24 10:24 ` [PATCH 2/6] [media] omap_vout: Improve a size determination in two functions SF Markus Elfring
2017-09-24 10:26 ` [PATCH 3/6] [media] omap_vout: Adjust a null pointer check " SF Markus Elfring
2017-09-24 10:28 ` [PATCH 4/6] [media] omap_vout: Fix a possible null pointer dereference in omap_vout_open() SF Markus Elfring
2017-09-24 10:30 ` [PATCH 5/6] [media] omap_vout: Delete an unnecessary variable initialisation " SF Markus Elfring
2017-09-24 10:33 ` [PATCH 6/6] [media] omap_vout: Delete two unnecessary variable initialisations in omap_vout_probe() SF Markus Elfring
2017-10-30  8:36 ` [PATCH 0/6] [media] omap_vout: Adjustments for three function implementations Hans Verkuil
2017-10-30  9:16   ` Adjustments for a lot of " SF Markus Elfring
2017-10-30  9:47     ` Julia Lawall
2017-10-30  9:57       ` Hans Verkuil
2017-10-30 10:40         ` SF Markus Elfring
2017-10-30 10:48           ` Hans Verkuil [this message]
2017-10-30 11:41             ` SF Markus Elfring
2017-11-26 19:06             ` SF Markus Elfring
2018-01-08 11:44             ` SF Markus Elfring
2018-02-02  9:55             ` SF Markus Elfring
2018-02-02 10:29               ` Hans Verkuil
2018-02-02 12:30                 ` SF Markus Elfring
2018-02-10  8:39                 ` SF Markus Elfring
2017-10-31  8:27         ` SF Markus Elfring

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=804550a6-1096-12f1-a0ec-1ccd6bcc191e@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=elfring@users.sourceforge.net \
    --cc=jack@suse.cz \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lstoakes@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mkaricheri@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).