All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
To: u-boot@lists.denx.de
Subject: [PATCH v1 2/2] drivers: pcie: add Broadcom IPROC PCIe RC driver
Date: Wed, 13 May 2020 08:05:42 +0530	[thread overview]
Message-ID: <CAHO=5PE83LjEM8hh7=M1E=PJXD2w4dg1n_kdCb5EusoyPe3V4Q@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ07j_6i6Tu8boxDAFVuTDp0TZp7EFGWC9NS+2hczuev4Q@mail.gmail.com>

Hi Simon,

On Wed, May 13, 2020 at 7:56 AM Simon Glass <sjg@chromium.org> wrote:
>
> Hi Rayagonda,
>
> On Tue, 12 May 2020 at 02:00, Rayagonda Kokatanur
> <rayagonda.kokatanur@broadcom.com> wrote:
> >
> > From: Srinath Mannam <srinath.mannam@broadcom.com>
> >
> > Add support for IPROC PAXC PCIe RC driver.
> >
> > Signed-off-by: Srinath Mannam <srinath.mannam@broadcom.com>
> > Signed-off-by: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
> > ---
> >  drivers/pci/Kconfig      |    7 +
> >  drivers/pci/Makefile     |    1 +
> >  drivers/pci/pcie_iproc.c | 1287 ++++++++++++++++++++++++++++++++++++++
> >  3 files changed, 1295 insertions(+)
> >  create mode 100644 drivers/pci/pcie_iproc.c
>
> Are you missing a change log?
This is a v1 patch.
Sorry I didn't get why change log is required.

Regards,
Rayagonda

>
> Regards,
> Simon

  reply	other threads:[~2020-05-13  2:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  7:59 [PATCH v1 0/2] add brcm iproc pcie driver Rayagonda Kokatanur
2020-05-12  7:59 ` [PATCH v1 1/2] drivers: pci: add api to get dma regions Rayagonda Kokatanur
2020-05-13  2:25   ` Simon Glass
2020-08-14 19:51   ` Tom Rini
2020-05-12  7:59 ` [PATCH v1 2/2] drivers: pcie: add Broadcom IPROC PCIe RC driver Rayagonda Kokatanur
2020-05-13  2:26   ` Simon Glass
2020-05-13  2:35     ` Rayagonda Kokatanur [this message]
2020-05-13  2:59   ` Simon Glass
2020-08-14 19:51   ` Tom Rini

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='CAHO=5PE83LjEM8hh7=M1E=PJXD2w4dg1n_kdCb5EusoyPe3V4Q@mail.gmail.com' \
    --to=rayagonda.kokatanur@broadcom.com \
    --cc=u-boot@lists.denx.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 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.