mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
To: Greg KH <greg@kroah.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	devel@driverdev.osuosl.org,
	Felipe Contreras <felipe.contreras@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] staging: tidspbridge for 2.6.38
Date: Wed, 5 Jan 2011 17:47:47 -0600	[thread overview]
Message-ID: <AANLkTikWpxq+35pLN_r6B214jcO2Ss2rEv0KA9bcMJFL@mail.gmail.com> (raw)
In-Reply-To: <20110105211847.GA16229@kroah.com>

On Wed, Jan 5, 2011 at 3:18 PM, Greg KH <greg@kroah.com> wrote:
> On Fri, Dec 24, 2010 at 02:15:43AM -0600, Omar Ramirez Luna wrote:
>> Hi Greg,
>>
>> This is the first pull request of changes for tidspbridge driver for 2.6.38,
>> I expect to make another request with at least one bug fix, but in the mean
>> time here it is the content for this one:
>>
>> The following changes since commit 90a8a73c06cc32b609a880d48449d7083327e11a:
>>
>>   Linux 2.6.37-rc7 (2010-12-21 11:26:40 -0800)
>>
>> are available in the git repository at:
>>   git://dev.omapzoom.org/pub/scm/tidspbridge/kernel-dspbridge.git dspbridge
>
> Ick, no.  Why did you base this on -rc7?  My staging-next branch is
> based on -rc5 at the moment, and I really see no need to merge the rest
> of them into the tree for no good reason at all.

wrongly though staging-next would be at rc7+ at the time you could
take a look to the patches

> Also, as you did send this before the merge window closed, but during
> the holidays, I couldn't get to it.  But in looking at this, it's going
> to have to wait for the next window, sorry, it's just too big, and too
> late.  You weren't expecting me to be working on kernel stuff during my
> holiday break, were you?

No I wasn't :)

> So, feel free to redo this against 2.6.38-rc1 when that comes out.

No problem then, but could you consider a 2nd pull with a compilation
fix (which will be introduced in 2.6.38, right now present in
linux-next), and a bug fix.

I'll send it and wait for any comments.

Regards,

Omar

  reply	other threads:[~2011-01-05 23:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24  8:15 Omar Ramirez Luna
2011-01-05 21:18 ` Greg KH
2011-01-05 23:47   ` Ramirez Luna, Omar [this message]
2011-01-05 23:57     ` Greg KH

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=AANLkTikWpxq+35pLN_r6B214jcO2Ss2rEv0KA9bcMJFL@mail.gmail.com \
    --to=omar.ramirez@ti.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=felipe.contreras@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®