All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-omap@vger.kernel.org,
	linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] omap iommu fixes for v3.0-rc
Date: Fri, 1 Jul 2011 03:05:26 -0700	[thread overview]
Message-ID: <20110701100525.GK23145@atomide.com> (raw)
In-Reply-To: <BANLkTikhZhUzyk=31cUOcV3Ygj=BHUrbew@mail.gmail.com>

* Ohad Ben-Cohen <ohad@wizery.com> [110701 00:46]:
> On Fri, Jul 1, 2011 at 10:00 AM, Tony Lindgren <tony@atomide.com> wrote:
> > These look like real fixes, but can you please update the commits
> > with something like "This fixes an issue with foo when doing bar".
> 
> Done, please tell me if it's OK now.

OK thanks!
 
> > Otherwise it's easy to claim that these are "fixes for features that
> > never worked" and it might be hard to justify them this late into
> > the -rc cycle.
> 
> It seems we did have these issues for quite some time, and these are not
> explicit 3.0 regressions. So they might vaguely fall into the "fixes
> for features that never worked" definition too in a sense.
> 
> If you prefer to take them into 3.1, that's OK too.

Let's do that then.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap iommu fixes for v3.0-rc
Date: Fri, 1 Jul 2011 03:05:26 -0700	[thread overview]
Message-ID: <20110701100525.GK23145@atomide.com> (raw)
In-Reply-To: <BANLkTikhZhUzyk=31cUOcV3Ygj=BHUrbew@mail.gmail.com>

* Ohad Ben-Cohen <ohad@wizery.com> [110701 00:46]:
> On Fri, Jul 1, 2011 at 10:00 AM, Tony Lindgren <tony@atomide.com> wrote:
> > These look like real fixes, but can you please update the commits
> > with something like "This fixes an issue with foo when doing bar".
> 
> Done, please tell me if it's OK now.

OK thanks!
 
> > Otherwise it's easy to claim that these are "fixes for features that
> > never worked" and it might be hard to justify them this late into
> > the -rc cycle.
> 
> It seems we did have these issues for quite some time, and these are not
> explicit 3.0 regressions. So they might vaguely fall into the "fixes
> for features that never worked" definition too in a sense.
> 
> If you prefer to take them into 3.1, that's OK too.

Let's do that then.

Regards,

Tony

  reply	other threads:[~2011-07-01 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  6:52 [GIT PULL] omap iommu fixes for v3.0-rc Ohad Ben-Cohen
2011-07-01  6:52 ` Ohad Ben-Cohen
2011-07-01  7:00 ` Tony Lindgren
2011-07-01  7:00   ` Tony Lindgren
2011-07-01  7:51   ` Ohad Ben-Cohen
2011-07-01  7:51     ` Ohad Ben-Cohen
2011-07-01 10:05     ` Tony Lindgren [this message]
2011-07-01 10:05       ` Tony Lindgren

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=20110701100525.GK23145@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.