linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	kernel-janitors@vger.kernel.org,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] PCI: tegra: replace devm_request_and_ioremap by devm_ioremap_resource
Date: Wed, 28 Aug 2013 15:27:32 +0200	[thread overview]
Message-ID: <20130828132731.GD604@ulmo> (raw)
In-Reply-To: <CAErSpo5LOig3KPGfyWJ1BWA61Ox3cyrguSo_XdVqw6SqxttXeA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Wed, Aug 28, 2013 at 07:02:16AM -0600, Bjorn Helgaas wrote:
> On Tue, Aug 27, 2013 at 12:03 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> >> On 08/27/2013 02:14 AM, Thierry Reding wrote:
> 
> >>> If Stephen's fine with it I suppose we could take pci-tegra.c
> >>> driver changes through the Tegra tree. But I think it'd be good if
> >>> we could still Cc you on patches so you're aware of what we're
> >>> doing (that is the same for all drivers drivers/pci/host/*). And
> >>> we're going to need your Acked-by on the patches as well.
> >
> > I think you have my Acked-by for this case already (from Aug 20).  And
> > feel free to copy me on anything you like; my delete key works well :)
> 
> I didn't mean for this to sound like "I'll just delete any email you
> send me"; I intended more like "feel free to copy me and if it's
> something I'm interested or knowledgeable about, I'll try to help and
> if not, it's easy for me to ignore it."

That's exactly the way I understood it. =)

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-28 13:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 11:20 [PATCH 0/7] replace devm_request_and_ioremap by devm_ioremap_resource Julia Lawall
2013-08-19 11:20 ` [PATCH 1/7] PCI: tegra: " Julia Lawall
2013-08-19 12:02   ` Thierry Reding
2013-08-19 12:07     ` Julia Lawall
2013-08-19 12:12       ` Thierry Reding
2013-08-19 12:15         ` Julia Lawall
2013-08-19 19:33           ` Thierry Reding
2013-08-19 20:56             ` Stephen Warren
2013-08-20  9:13             ` Julia Lawall
2013-08-20 16:26               ` Bjorn Helgaas
2013-08-20 18:53                 ` Stephen Warren
2013-08-20 19:31                   ` Thierry Reding
2013-08-19 20:04     ` Bjorn Helgaas
2013-08-19 20:12       ` Thierry Reding
2013-08-19 20:49         ` Bjorn Helgaas
2013-08-27  8:14           ` Thierry Reding
2013-08-27 16:11             ` Stephen Warren
2013-08-27 18:03               ` Bjorn Helgaas
2013-08-28 13:02                 ` Bjorn Helgaas
2013-08-28 13:27                   ` Thierry Reding [this message]
2013-08-28 13:31                 ` Thierry Reding

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=20130828132731.GD604@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=Julia.Lawall@lip6.fr \
    --cc=bhelgaas@google.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.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).