From: Greg KH <greg@kroah.com>
To: matt mooney <mfmooney@gmail.com>
Cc: matt mooney <mfm@muteddisk.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: usbip: replace usbip_u{dbg,err,info} and printk with dev_ and pr_
Date: Thu, 19 May 2011 21:12:44 -0700 [thread overview]
Message-ID: <20110520041244.GA986@kroah.com> (raw)
In-Reply-To: <BANLkTi=FZ57TrOa48qxkO6Myf0pwgtPp7g@mail.gmail.com>
On Thu, May 19, 2011 at 07:30:39PM -0700, matt mooney wrote:
> On Thu, May 19, 2011 at 5:24 PM, Greg KH <greg@kroah.com> wrote:
> > On Thu, May 19, 2011 at 05:17:45PM -0700, matt mooney wrote:
> >> On Thu, May 19, 2011 at 5:00 PM, Greg KH <greg@kroah.com> wrote:
> >> > Also, the merge window for the .40 tree for the staging tree is now
> >> > closed, so I'll only take bugfixes for the usbip code for now.
> >>
> >> The userspace code isn't getting merged in .40, is it? Because my
> >> patch "staging: usbip: userspace: stub_driver.c: update kernel module
> >> name" actually relies on a change in my own tree, so I made a mistake
> >> by thinking that it was needed right away to get the userspace tools
> >> working.
> >
> > It's in my tree, so yes. You can send me patches to fix the problem, as
> > I would recommend :)
>
> Can I send you a 10 patch series (or 9 if you apply the patch in this
> thread)? The changes I have that fix that are towards the end. The
> problem is a lot of my changes rely on the patch sent in this thread
> and one that follows it, so to avoid any conflicts it is easiest (at
> least for me :) to just send the whole series. They have been tested
> and pretty much leave usbip in the state it was originally in.
I don't know, I would have to see the patches. Please send them on.
thanks,
greg k-h
next prev parent reply other threads:[~2011-05-20 4:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 23:47 [PATCH] staging: usbip: replace usbip_u{dbg,err,info} and printk with dev_ and pr_ matt mooney
2011-05-20 0:00 ` Greg KH
2011-05-20 0:17 ` matt mooney
2011-05-20 0:24 ` Greg KH
2011-05-20 2:30 ` matt mooney
2011-05-20 4:12 ` Greg KH [this message]
2011-05-20 4:31 ` matt mooney
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=20110520041244.GA986@kroah.com \
--to=greg@kroah.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfm@muteddisk.com \
--cc=mfmooney@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