public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5] colibri_vf: Add board_usb_phy_mode function
Date: Fri, 8 Jan 2016 13:11:27 +0100	[thread overview]
Message-ID: <201601081311.27838.marex@denx.de> (raw)
In-Reply-To: <20160108055041.GA2977@Sanchayan-Arch.toradex.int>

On Friday, January 08, 2016 at 06:50:41 AM, maitysanchayan at gmail.com wrote:
> Hello,
> 
> On 16-01-07 22:12:29, Stefano Babic wrote:
> > Hi,
> > 
> > On 07/01/2016 21:02, maitysanchayan at gmail.com wrote:
> > > Hello Stefano,
> > > 
> > > Ping?
> > > 
> > > I just checked the master branch and this has not been picked up yet.
> > 
> > Can you check ? I see:
> > 
> > commit 01a8cf91513981d05bf89840d768e9c060ee998b
> > Author: Sanchayan Maity <maitysanchayan@gmail.com>
> > Date:   Thu Nov 12 11:47:35 2015 +0530
> > 
> >     colibri_vf: Add board_usb_phy_mode function
> 
> Yes, this seems to be present but the first and second patch in the series
> which make changes to the ehci-vf driver are not present.

But this is only a single patch here , even the subject indicates so ... ?

Best regards,
Marek Vasut

  reply	other threads:[~2016-01-08 12:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 12:58 [U-Boot] [PATCH 1/3] usb: host: ehci-vf: Remove hardcoded USB host client configuration Sanchayan Maity
2015-10-26 12:58 ` [U-Boot] [PATCH 2/3] usb: host: ehci-vf: Implement board_usb_phy_mode weak function Sanchayan Maity
2016-01-08 12:22   ` maitysanchayan at gmail.com
2016-01-08 14:02     ` Marek Vasut
2015-10-26 12:58 ` [U-Boot] [PATCH 3/3] colibri_vf: Add board_usb_phy_mode function Sanchayan Maity
2015-10-27  9:18   ` Marek Vasut
2015-10-27 11:34     ` maitysanchayan at gmail.com
2015-10-29 10:15   ` [U-Boot] [PATCH v2] " Sanchayan Maity
2015-10-29 17:25     ` Marek Vasut
2015-10-30 12:26     ` [U-Boot] [PATCH v3] " Sanchayan Maity
2015-10-30 13:20       ` Marek Vasut
2015-11-06  7:00         ` maitysanchayan at gmail.com
2015-11-06 15:00           ` Marek Vasut
2015-10-30 16:12       ` Stefan Agner
2015-10-30 16:24         ` Marek Vasut
2015-10-30 16:26           ` Stefan Agner
2015-10-30 17:07             ` Marek Vasut
2015-11-09 14:59       ` [U-Boot] [PATCH v4] " Sanchayan Maity
2015-11-09 15:22         ` Marek Vasut
2015-11-12  6:17         ` [U-Boot] [PATCH v5] " Sanchayan Maity
2015-11-24 10:23           ` maitysanchayan at gmail.com
2015-11-24 10:30             ` Marek Vasut
2015-11-24 10:37             ` Stefano Babic
2015-11-24 10:38               ` maitysanchayan at gmail.com
2016-01-07 20:02               ` maitysanchayan at gmail.com
2016-01-07 21:12                 ` Stefano Babic
2016-01-08  5:50                   ` maitysanchayan at gmail.com
2016-01-08 12:11                     ` Marek Vasut [this message]
2016-01-08 12:18                       ` maitysanchayan at gmail.com
2016-01-08 12:25                         ` Marek Vasut
2015-10-26 19:19 ` [U-Boot] [PATCH 1/3] usb: host: ehci-vf: Remove hardcoded USB host client configuration Marek Vasut
2015-10-27  3:28   ` maitysanchayan at gmail.com
2016-01-08 12:20 ` maitysanchayan at gmail.com
2016-01-08 12:26   ` Marek Vasut
2016-01-08 12:26     ` maitysanchayan at gmail.com
2016-01-08 14:02   ` Marek Vasut

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=201601081311.27838.marex@denx.de \
    --to=marex@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox