linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: David Brown <davidb@codeaurora.org>
Cc: Daniel Walker <dwalker@fifo99.com>,
	Bryan Huntsman <bryanh@codeaurora.org>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: msm: Remove MSM7x00 support
Date: Thu, 1 Dec 2011 20:19:50 +0000	[thread overview]
Message-ID: <20111201201950.GE9581@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111201194353.GA24293@huya.qualcomm.com>

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.

  parent reply	other threads:[~2011-12-01 20:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01  0:29 [PATCH 1/3] ARM: msm: Remove MSM7x00 support David Brown
2011-12-01  0:29 ` [PATCH 2/3] gpio_msm: remove support for MSM7x01 David Brown
2011-12-01  0:29 ` [PATCH 3/3] ARM: msm: Remove cpu_is test for msm7201 soc David Brown
2011-12-01 15:17 ` [PATCH 1/3] ARM: msm: Remove MSM7x00 support Daniel Walker
2011-12-01 18:17   ` David Brown
2011-12-01 18:39     ` Daniel Walker
2011-12-01 19:27       ` David Brown
2011-12-01 19:33         ` Daniel Walker
2011-12-01 19:43           ` David Brown
2011-12-01 19:53             ` Daniel Walker
2011-12-01 20:17               ` David Brown
2011-12-01 20:19             ` Russell King - ARM Linux [this message]
2011-12-01 20:25               ` Daniel Walker
2011-12-01 20:35                 ` Russell King - ARM Linux
2011-12-01 20:49                   ` Daniel Walker
2011-12-01 21:03                     ` Russell King - ARM Linux
2011-12-01 21:34                       ` Daniel Walker
2011-12-01 20:26               ` David Brown
2011-12-01 20:32                 ` Daniel Walker
2011-12-02 13:17                 ` Denis 'GNUtoo' Carikli
2011-12-02 15:26                   ` David Brown

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=20111201201950.GE9581@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=bryanh@codeaurora.org \
    --cc=davidb@codeaurora.org \
    --cc=dwalker@fifo99.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.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).