linux-next tree addition request (fbdev)
Subsystems (2)
Hi Stephen,
can you please add
git://github.com/schandinat/linux-2.6.git fbdev-next
to linux-next. It collects patches for the frame buffer subsystem. Can you please add the [email protected] mailing list as additional contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated patches that will conflict with the newer versions.
Thanks,
Florian Tobias Schandinat
Hi Florian,
Quoted 11 lines · On Wed, 24 Aug 2011 13:40:46 +0000 Florian Tobias Schandinat…
can you please add
git://github.com/schandinat/linux-2.6.gitfbdev-nextto linux-next. It collects patches for the frame buffer subsystem. Can you please add the [email protected] mailing list as additional contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated patches that will conflict with the newer versions.
OK, Paul is still listed as the frame buffer subsystem maintainer, so I will need an Ack from him. When I get that, I will replace his tree with yours. I assume someone will update the MAINTAINERS file.
I also have another tree from Paul (called fbdev-current) that contained fixes for Linus' current release. I also assume that that tree will be dropped (unless you have a new version of that as well).
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Hi Florian,
Quoted 14 lines · On Thu, 25 Aug 2011 00:33:53 +1000 Stephen Rothwell <[email protected]>…
Quoted 11 lines · On Wed, 24 Aug 2011 13:40:46 +0000 Florian Tobias Schandinat…
can you please add
git://github.com/schandinat/linux-2.6.gitfbdev-nextto linux-next. It collects patches for the frame buffer subsystem. Can you please add the [email protected] mailing list as additional contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated patches that will conflict with the newer versions.
Quoted 7 lines
OK, Paul is still listed as the frame buffer subsystem maintainer, so I will need an Ack from him. When I get that, I will replace his tree with yours. I assume someone will update the
MAINTAINERSfile.I also have another tree from Paul (called fbdev-current) that contained fixes for Linus' current release. I also assume that that tree will be dropped (unless you have a new version of that as well).
Ping? Anyone?
Signature · 3 lines
Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Quoted 21 lines · Stephen Rothwell
Hi Florian,
Quoted 18 lines · On Thu, 25 Aug 2011 00:33:53 +1000 Stephen Rothwell <[email protected]>…
Quoted 11 lines · On Wed, 24 Aug 2011 13:40:46 +0000 Florian Tobias Schandinat…
can you please add
git://github.com/schandinat/linux-2.6.gitfbdev-nextto linux-next. It collects patches for the frame buffer subsystem. Can you please add the [email protected] mailing list as additional contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated patches that will conflict with the newer versions.
OK, Paul is still listed as the frame buffer subsystem maintainer, so I will need an Ack from him. When I get that, I will replace his tree with yours. I assume someone will update the
MAINTAINERSfile.
Quoted 6 lines
Quoted 3 lines
I also have another tree from Paul (called fbdev-current) that contained fixes for Linus' current release. I also assume that that tree will be dropped (unless you have a new version of that as well).
Ping? Anyone?
As long as Florian is taking care of the backlog of the stuff that is already sitting in that branch, I have no problems with it being dropped. I'm not planning on pushing any updates to it anyways.
Hi Paul,
Quoted 26 lines · Paul Mundt
Quoted 25 lines · Stephen Rothwell
Hi Florian,
Quoted 21 lines · On Thu, 25 Aug 2011 00:33:53 +1000 Stephen Rothwell <[email protected]>…
Quoted 11 lines · On Wed, 24 Aug 2011 13:40:46 +0000 Florian Tobias Schandinat…
can you please add
git://github.com/schandinat/linux-2.6.gitfbdev-nextto linux-next. It collects patches for the frame buffer subsystem. Can you please add the [email protected] mailing list as additional contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated patches that will conflict with the newer versions.
OK, Paul is still listed as the frame buffer subsystem maintainer, so I will need an Ack from him. When I get that, I will replace his tree with yours. I assume someone will update the
MAINTAINERSfile.I also have another tree from Paul (called fbdev-current) that contained fixes for Linus' current release. I also assume that that tree will be dropped (unless you have a new version of that as well).
Quoted 5 lines
Quoted 2 lines
Ping? Anyone?
As long as Florian is taking care of the backlog of the stuff that is already sitting in that branch, I have no problems with it being dropped. I'm not planning on pushing any updates to it anyways.
Merged the remaining patches of your branch.
Thanks,
Florian Tobias Schandinat
Hi Florian,
Quoted 11 lines · On Wed, 24 Aug 2011 13:40:46 +0000 Florian Tobias Schandinat…
can you please add
git://github.com/schandinat/linux-2.6.gitfbdev-nextto linux-next. It collects patches for the frame buffer subsystem. Can you please add the [email protected] mailing list as additional contact for warnings/errors/problems?
You probably want to drop Paul's fbdev branches as they contain some outdated patches that will conflict with the newer versions.
I have replced Paul;s fbdev tree with yours and dropped his fbdev-current tree.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Signature · 15 lines
Cheers, Stephen Rothwell [email protected] Legal Stuff: By participating in linux-next, your subsystem tree contributions are public and will be included in the linux-next trees. You may be sent e-mail messages indicating errors or other issues when the patches/commits from your subsystem tree are merged and tested in linux-next. These messages may also be cross-posted to the linux-next mailing list, the linux-kernel mailing list, etc. The linux-next tree project and IBM (my employer) make no warranties regarding the linux-next project, the testing procedures, the results, the e-mails, etc. If you don't agree to these ground rules, let me know and I'll remove your tree from participation in linux-next.