mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "balbi@ti.com" <balbi@ti.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] usb: isp1760: add peripheral/device controller chip id
Date: Mon, 9 Mar 2015 11:13:53 -0500	[thread overview]
Message-ID: <20150309161353.GE3739@saruman.tx.rr.com> (raw)
In-Reply-To: <54FDC30E.3050803@arm.com>

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

On Mon, Mar 09, 2015 at 03:58:06PM +0000, Sudeep Holla wrote:
> Hi Filipe,
> 
> On 09/03/15 15:49, Felipe Balbi wrote:
> >On Wed, Mar 04, 2015 at 03:56:12PM +0000, Sudeep Holla wrote:
> >>
> >>
> >>On 26/02/15 18:53, Laurent Pinchart wrote:
> >>>Hi Sudeep,
> >>>
> >>>Thank you for the patch.
> >>>
> >>>On Thursday 26 February 2015 11:47:57 Sudeep Holla wrote:
> >>>>As per the SAF1761 data sheet[0], the DcChipID register represents
> >>>>the hardware version number (0001h) and the chip ID (1582h) for the
> >>>>Peripheral Controller.
> >>>>
> >>>>However as per the ISP1761 data sheet[1], the DcChipID register
> >>>>represents the hardware version number (0015h) and the chip ID (8210h)
> >>>>for the Peripheral Controller.
> >>>>
> >>>>This patch adds support for both the chip ID values.
> >>>>
> >>>>[0] http://www.nxp.com/documents/data_sheet/SAF1761.pdf
> >>>>[1] http://pdf.datasheetcatalog.com/datasheets2/74/742102_1.pdf
> >>>>
> >>>>Cc: Felipe Balbi <balbi@ti.com>
> >>>>Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >>>>Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> >>>
> >>>Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >>>
> >>
> >>Thanks. I assume Felipe will pick this up.
> >
> >I will, but I need Laurent's Ack.
> >
> 
> I am confused, Laurent has already Ack-ed(see above) this patch[0]
> as well as [1].

yeah, just came back from vacations, going through my inbox.

-- 
balbi

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

      reply	other threads:[~2015-03-09 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 17:53 [PATCH] usb: isp1760: fix " Sudeep Holla
2015-02-25 22:27 ` Laurent Pinchart
2015-02-26 10:24   ` Sudeep Holla
2015-02-26 11:47 ` [PATCH v2] usb: isp1760: add " Sudeep Holla
2015-02-26 18:53   ` Laurent Pinchart
2015-03-04 15:56     ` Sudeep Holla
2015-03-04 16:11       ` Laurent Pinchart
2015-03-04 17:04         ` Sudeep Holla
2015-03-05 11:12           ` Laurent Pinchart
2015-03-09 15:49       ` Felipe Balbi
2015-03-09 15:58         ` Sudeep Holla
2015-03-09 16:13           ` Felipe Balbi [this message]

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=20150309161353.GE3739@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sudeep.holla@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome