linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] PHY: For 5.1 -rc
Date: Wed, 17 Apr 2019 14:19:56 +0530	[thread overview]
Message-ID: <fd529200-fbb6-a513-940b-a415ac11bb72@ti.com> (raw)
In-Reply-To: <20190416103059.GA8292@kroah.com>

Hi Greg,

On 16/04/19 4:00 PM, Greg Kroah-Hartman wrote:
> On Wed, Apr 03, 2019 at 10:13:53AM +0530, Kishon Vijay Abraham I wrote:
>> Hi Greg,
>>
>> Please find the pull request for 5.1 -rc cycle below.
>>
>> It fixes PHY programming sequence in phy-ti-pipe3 driver to align with
>> TRM, requests IRQ only for OTG in phy-rcar-gen3-usb2 and a bunch of
>> other linker errors and compilation warnings seen in randconfig.
>>
>> Please see the complete list of changes in the tag message below and let
>> me know if I have to make any modifications.
>>
>> Thanks
>> Kishon
>>
>> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>>
>>   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git tags/phy-for-5.1-rc
>>
>> for you to fetch changes up to d5d60c3f25ab52de7c5dfd31f584f190b754629e:
>>
>>   phy: fix platform_no_drv_owner.cocci warnings (2019-04-03 10:02:20 +0530)
>>
>> ----------------------------------------------------------------
>> phy: for 5.1-rc
>>
>>   *) Follow TRM sequence in phy-ti-pipe3 driver to ensure DPLL & PHY
>>      operates correctly over the entire temperature range
>>   *) Fix missing bit-wise 'OR' operator in ti-pipe3 driver
>>   *) Fix to request IRQ only for OTG in phy-rcar-gen3-usb2 driver
>>   *) Fix linker errors and compilation warnings got with randconfig
>>   *) Fix sparse warnings and .cocci warnings
>>
>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>>
>> ----------------------------------------------------------------
>> Arnd Bergmann (3):
>>       phy: allwinner: allow compile testing
>>       phy: ti: usb2: fix OMAP_CONTROL_PHY dependency
>>       phy: mapphone-mdm6600: add gpiolib dependency
>>
>> Colin Ian King (1):
>>       phy: ti-pipe3: fix missing bit-wise or operator when assigning val
>>
>> Fabrizio Castro (1):
>>       phy: renesas: rcar-gen3-usb2: No need to request IRQ for non-OTG
>>
>> Roger Quadros (4):
>>       phy: ti-pipe3: Introduce mode property in driver data
>>       phy: ti-pipe3: improve DPLL stability for SATA & USB
>>       phy: ti-pipe3: Fix SATA & USB PHY power up sequence
>>       phy: ti-pipe3: Fix PCIe power up sequence
>>
>> Tony Lindgren (1):
>>       phy: phy-twl4030-usb: Fix cable state handling
>>
>> YueHaibing (3):
>>       phy: rockchip-typec: Make usb3_pll_cfg and dp_pll_cfg static
>>       phy: qcom-ufs: Make ufs_qcom_phy_disable_iface_clk static
>>       phy: fix platform_no_drv_owner.cocci warnings
>>
>>  drivers/phy/allwinner/Kconfig              |   9 ++--
>>  drivers/phy/marvell/phy-mvebu-a3700-utmi.c |   1 -
>>  drivers/phy/motorola/Kconfig               |   2 +-
>>  drivers/phy/qualcomm/phy-qcom-ufs.c        |   2 +-
>>  drivers/phy/renesas/phy-rcar-gen3-usb2.c   |  27 ++++++------
>>  drivers/phy/rockchip/phy-rockchip-typec.c  |   4 +-
>>  drivers/phy/ti/Kconfig                     |   2 +-
>>  drivers/phy/ti/phy-ti-pipe3.c              | 362 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------------
> 
> That's a lot of changes so late in the release cycle for one driver.
> Are you sure those are not 5.2-rc1 things?

hmm, I'll add ti-pipe3 changes for 5.2-rc1 and send you v2 for this pull request.

Thanks
Kishon

      reply	other threads:[~2019-04-17  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03  4:43 [GIT PULL] PHY: For 5.1 -rc Kishon Vijay Abraham I
2019-04-16 10:30 ` Greg Kroah-Hartman
2019-04-17  8:49   ` Kishon Vijay Abraham I [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=fd529200-fbb6-a513-940b-a415ac11bb72@ti.com \
    --to=kishon@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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).