From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: linux-next for fbdev
Date: Fri, 06 Feb 2015 04:44:20 +0000 [thread overview]
Message-ID: <20150206043220.GA2707@sudip-PC> (raw)
In-Reply-To: <54D38B76.5070005@ti.com>
On Thu, Feb 05, 2015 at 05:25:42PM +0200, Tomi Valkeinen wrote:
> Hi,
>
> On 05/02/15 17:20, Sudip Mukherjee wrote:
> > Hi,
> > I have noticed that we do not have anything called fbdev-next so patches to fbdev does not appear in linux-next, but instead waits for the merge window. That may be because you might not have enough time to maintain a separate tree or any other reason.
> > Can i help in any way to have a fbdev-next tree? I can have a tree in my server, where i can apply the patches that you are queuing for the next merge window (usually you will send reply to the list that it is queued). And that tree can act as fbdev-next.
> >
> > This was just an idea, and but I am willing to help you in any way to have a fbdev-next.
>
> I have 'for-next' branch in my tree
> git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git which gets
> pulled into linux-next, and that's where I push fbdev patches.
>
The reason for my mail Stephen in his mail "linux-next: tidy up of trees" mentioned that fbdev is not getting updated. But now when I am checking i am seeing my fbdev patches in linux-next. I should have checked before sending you the mail.
Sorry for the noise.
Sudip
> Tomi
>
>
prev parent reply other threads:[~2015-02-06 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 15:25 linux-next for fbdev Tomi Valkeinen
2015-02-05 15:32 ` Sudip Mukherjee
2015-02-06 4:44 ` Sudip Mukherjee [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=20150206043220.GA2707@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=linux-fbdev@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 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).