From: Tejun Heo <tj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH RESEND] char_dev: add cdev->release() and convert cdev_alloc() to use it
Date: Thu, 20 Nov 2008 15:28:46 +0900 [thread overview]
Message-ID: <4925039E.8020907@kernel.org> (raw)
In-Reply-To: <20081120055450.GA10821@kroah.com>
Greg KH wrote:
>> Hmmm... if you can use this change, I think you can push it through
>> whatever tree you push patches through, things can be taken care of when
>> merging or we can put it in Greg's tree and ask Miklos to pull from the
>> tree first but Greg doesn't keep a stable tree.
>
> I don't keep a stable tree? What do you mean? It's a quilt tree, and
> it does get included in -next, so I think it does work :)
Heh... I meant stable (in the sense that it doesn't get rebased) git
tree which Miklos can pull from.
> Send it to me again and I'll push it through my tree if no one else
> objects.
Yeap, will resend it and let you and Miklos sort it out.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-11-20 6:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:36 [PATCH RESEND] char_dev: add cdev->release() and convert cdev_alloc() to use it Tejun Heo
2008-08-28 16:47 ` Greg KH
2008-08-28 16:56 ` Tejun Heo
2008-08-28 17:38 ` Greg KH
2008-08-28 17:44 ` Tejun Heo
2008-08-28 17:48 ` Greg KH
2008-08-28 17:55 ` Tejun Heo
2008-08-28 18:17 ` Greg KH
2008-11-13 8:58 ` Tejun Heo
[not found] ` <492136F5.8010903@kernel.org>
[not found] ` <20081117171717.GB31306@kroah.com>
[not found] ` <49221CE8.1050402@kernel.org>
2008-11-18 1:40 ` Tejun Heo
2008-11-18 13:44 ` Boaz Harrosh
2008-11-18 15:58 ` Tejun Heo
2008-11-19 17:59 ` Miklos Szeredi
2008-11-20 5:54 ` Greg KH
2008-11-20 6:28 ` Tejun Heo [this message]
2008-11-20 11:45 ` Tejun Heo
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=4925039E.8020907@kernel.org \
--to=tj@kernel.org \
--cc=bharrosh@panasas.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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