linux-kernel - Re: [PATCH 1/4] usb: phy: rename nop_usb_xceiv => usb_phy_gen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Jul 2013 00:56:51 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	Felipe Balbi <balbi@...com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, george.cherian@...com,
	Linux OMAP Mailing List <linux-omap@...r.kernel.org>
Subject: Re: [PATCH 1/4] usb: phy: rename nop_usb_xceiv => usb_phy_gen_xceiv

* Sebastian Andrzej Siewior <bigeasy@...utronix.de> [130730 00:41]:
> On 07/30/2013 09:08 AM, Tony Lindgren wrote:
> > Looking at this patch there's a pretty high probability of introducing
> > pointless merge conflicts.
> > 
> > How about do the platform data related changes as a separate follow-up
> > series? You can typically do this by keeping the old features around,
> > then doing a separate series to rename or remove the users later on.
> > This will remove the dependency between platform data and the driver
> > changes.
> 
> I can do this. This will work of for the driver name but not for the
> name the platform_data struct. To address this part you could create a
> separate branch on top of -rc3 or so which contains only this change(s)
> and Felipe and you merge this branch so there won't be any conflicts.

A separate minimal branch against -rc3 sounds good to me.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/