linux-kernel - Re: [PATCH 1/3] ARM: msm: Remove MSM7x00 support

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]

Message-ID: <20111201202632.GA25247@huya.qualcomm.com>
Date:	Thu, 1 Dec 2011 12:26:32 -0800
From:	David Brown <davidb@...eaurora.org>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	David Brown <davidb@...eaurora.org>,
	Daniel Walker <dwalker@...o99.com>,
	Bryan Huntsman <bryanh@...eaurora.org>,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] ARM: msm: Remove MSM7x00 support

On Thu, Dec 01, 2011 at 08:19:50PM +0000, Russell King - ARM Linux wrote:
> On Thu, Dec 01, 2011 at 11:43:53AM -0800, David Brown wrote:
> > On Thu, Dec 01, 2011 at 11:33:12AM -0800, Daniel Walker wrote:
> > > On Thu, 2011-12-01 at 11:27 -0800, David Brown wrote:
> > > > On Thu, Dec 01, 2011 at 10:39:05AM -0800, Daniel Walker wrote:
> > > > 
> > > > > > If someone is willing to step up and make it work, then we can keep it
> > > > > > around.  My only G1 is fried, so I have no way to do anything other
> > > > > > than keep it compiling.
> > > > > 
> > > > > Unfortunately, You can't remove it regardless of whether or not you have
> > > > > one to test on.. Your job is to do the best you can to keep it working
> > > > > and maintained. If you don't have one then you can't boot test but you
> > > > > still have to your best to keep it as close to working as possible.
> > > > 
> > > > I was trying to get an idea if anyone uses the target.  If people
> > > > want the target around, we can just ignore my patches to remove it.
> > > 
> > > Please don't ever do this again.
> > 
> > That's awfully harsh.  I sent an email a few weeks back asking about
> > removing the target, and I only got one positive response.  Sometimes
> > sending a patch is the best way to get a reaction.
> 
> That's pretty normal for just 'asking' about doing something.
> 
> You've done the right thing - if you ask, people treat your message as
> low priority and don't bother replying in the hope that nothing will
> happen.
> 
> However, if you send a patch to delete a platform, people treat it as
> most urgent because if they care they need to speak up to actually stop
> it happening.  (Even if you intend to only actually submit it in 6
> months time or so - but don't mention that in the initial posting!)
> 
> Now, the obvious question to ask now is this: as you sent your question,
> and Daniel obviously objects, was Daniel one of your respondants?  If
> not, then he carries some of the blame for this patch being created
> in the first place by having missed the email/not replied/etc.

Yeah, my mistake was forgetting to CC Daniel on the original question
about removing the target.

And I've learned what I needed to now: someone does still care about
the target.

David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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/