linux-kernel - Re: [PATCH 0/1 for 4.4-rc8] ARM: Fix broken USB support in sunxi

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 01 Jan 2016 14:59:41 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Timo Sigurdsson <public_timo.s@...entcreek.de>
Cc:	linux-arm-kernel@...ts.infradead.org, arm@...nel.org,
	linux@....linux.org.uk, maxime.ripard@...e-electrons.com,
	wens@...e.org, tyler.baker@...aro.org, info@...hard-bertelsmann.de,
	net147@...il.com, carlo@...one.org, linux-kernel@...r.kernel.org,
	hdegoede@...hat.com, david@...loh.id.au
Subject: Re: [PATCH 0/1 for 4.4-rc8] ARM: Fix broken USB support in sunxi_defconfig

On Friday 01 January 2016 14:25:01 Timo Sigurdsson wrote:
> Hi Arnd,
> 
> Arnd Bergmann schrieb am 31.12.2015 16:46:
> 
> > On Tuesday 29 December 2015 02:47:32 Timo Sigurdsson wrote:
> >> Here is a late patch aimed for 4.4-rc8 (or 4.4). It would be nice if this   
> >> could make it into 4.4 in order to avoid unpleasent surprises (and
> >> subsequent questions) with builds based on sunxi_defconfig. At the moment,
> >> some boards (e.g. LeMaker BananaPi) are left with non-functional USB ports
> >> as a newly added driver is required to power them.
> > 
> > It's a bit confusing to send a patch to so many recipients, that usually
> > leads to nobody applying it. I can put it into the fixes branch in arm-soc
> > but need an Ack from the sunxi maintainer(s).
> 
> Sorry, I didn't know any better. Almost all recipients came from the
> get-maintainers script (which I thought were mandatory to include). What's
> the recommended way in such cases?

Just put everyone on Cc, and have the most appropriate recipient (which you
expect to act on the path) as 'To'. Also, address that person in the
cover letter so they know they should act on it, e.g. "Hi Maxime,
can you pick up this patch and forward it to arm-soc?".
 
> I already prepared and tested a patch for multi_v7_defconfig which I'll
> send to the same recipients as before just for the sake of not shutting
> out people that were previously addressed in this conversation.

Ok, thanks.

	Arnd
--
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/