linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Nehal-bakulchandra.Shah@amd.com
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-i2c <linux-i2c@vger.kernel.org>,
	Sandeep.Singh@amd.com, Shyam-sundar.S-k@amd.com,
	kai.heng.feng@canonical.com
Subject: Re: [PATCH] i2c:amd I2C Driver based on PCI Interface for upcoming platform
Date: Mon, 4 Jun 2018 12:15:38 -0500	[thread overview]
Message-ID: <CAErSpo6SvtKL6HsPGn2KM5Tw+oadHZXWeq=aLMA+1pyrBfBA1Q@mail.gmail.com> (raw)
In-Reply-To: <SN1PR12MB257592515E4A436078D43E68A0670@SN1PR12MB2575.namprd12.prod.outlook.com>

On Mon, Jun 4, 2018 at 11:33 AM Shah, Nehal-bakulchandra
<Nehal-bakulchandra.Shah@amd.com> wrote:
>
> Hi All,
>
> Please help in reviewing the patch.

If you'd like PCI review, please post the patches to linux-pci@vger.kernel.=
org.

> -----Original Message-----
> From: linux-i2c-owner@vger.kernel.org [mailto:linux-i2c-owner@vger.kernel=
.org] On Behalf Of Wolfram Sang
> Sent: Friday, June 1, 2018 3:13 AM
> To: Shah, Nehal-bakulchandra <Nehal-bakulchandra.Shah@amd.com>
> Cc: linux-i2c@vger.kernel.org; Singh, Sandeep <Sandeep.Singh@amd.com>; S-=
k, Shyam-sundar <Shyam-sundar.S-k@amd.com>; Kai Heng Feng <kai.heng.feng@ca=
nonical.com>
> Subject: Re: [PATCH] i2c:amd I2C Driver based on PCI Interface for upcomi=
ng platform
>
> Hi,
>
> > I am waiting for the feedback on this patch. It has been there since
> > long time. Can you please provide the feedback.
>
> Well, reviewing drivers is a community effort these days. While I am part=
 of this community, I am surely not the only one. So, please ask the list f=
or help (rather than me personally). Furthermore, I think I am not the righ=
t person here to ask for help. I don't know much about PCI & ACPI. We have =
dedicated I2C-ACPI maintainers, maybe they have some bandwidth for review?
>
> That being said: yes, it is sad that you need to wait this long; yet I si=
mply can't fill up all the resource problems we have here.
>
> Thanks,
>
>    Wolfram
>

  reply	other threads:[~2018-06-04 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1524928597-23312-1-git-send-email-Nehal-bakulchandra.Shah@amd.com>
     [not found] ` <SN1PR12MB257536FC4322C1D3D6F2F972A06C0@SN1PR12MB2575.namprd12.prod.outlook.com>
     [not found]   ` <20180531214311.i6s5xginjgevkwoe@ninjato>
2018-06-04 16:33     ` [PATCH] i2c:amd I2C Driver based on PCI Interface for upcoming platform Shah, Nehal-bakulchandra
2018-06-04 17:15       ` Bjorn Helgaas [this message]
2018-06-07 10:22         ` Shah, Nehal-bakulchandra
2018-06-07 13:32           ` Bjorn Helgaas

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='CAErSpo6SvtKL6HsPGn2KM5Tw+oadHZXWeq=aLMA+1pyrBfBA1Q@mail.gmail.com' \
    --to=bhelgaas@google.com \
    --cc=Nehal-bakulchandra.Shah@amd.com \
    --cc=Sandeep.Singh@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=wsa@the-dreams.de \
    /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).