All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Paul Mundt <lethal@linux-sh.org>, Jeff Garzik <jgarzik@pobox.com>,
	Al Viro <viro@ftp.linux.org.uk>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pata_platform: fallout from set_mode() change
Date: Tue, 30 Jan 2007 09:12:13 -0500	[thread overview]
Message-ID: <45BF523D.9060002@pobox.com> (raw)
In-Reply-To: <20070130140518.GB26984@linux-sh.org>

Paul Mundt wrote:
> On Tue, Jan 30, 2007 at 08:36:28AM -0500, Jeff Garzik wrote:
>> Al Viro wrote:
>>> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>> This is already in the queue via Andrew, who caught the same problem.
>>
>> Sometimes it seems like you and Andrew are the only people to build on 
>> non-x86 these days...
>>
> This is the first I've heard of this or the changes that caused this,
> while I do build current git on a pretty much daily basis, -mm doesn't
> get nearly as much testing.
> 
> There are many people who build on non-x86 every day, there are rather
> less people who have the bandwidth for -mm as well as current git or
> for tracking down changes that haven't made it upstream to make sure
> everything plays nice.
> 
> If you want immediate action, I suggest you CC the authors of the drivers
> when there's changes they should be made aware of, rather than deferring
> to hand-waving generalizations about how no one does any testing after
> the fact.

The change in question is in the current -git.  But my comment was 
largely self-critical, since /I/ applied the patch in question that 
broke on non-x86.

	Jeff




  reply	other threads:[~2007-01-30 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 13:23 [PATCH] pata_platform: fallout from set_mode() change Al Viro
2007-01-30 13:36 ` Jeff Garzik
2007-01-30 14:05   ` Paul Mundt
2007-01-30 14:12     ` Jeff Garzik [this message]
2007-01-30 16:13 ` Alan

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=45BF523D.9060002@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ftp.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.