mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
To: "Russell King - ARM Linux" <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3.1-rc1] ARM: entry: fix wrong parameter used in do_thumb_abort
Date: Thu, 8 Sep 2011 20:02:11 +0200	[thread overview]
Message-ID: <201109082002.11635.jkrzyszt@tis.icnet.pl> (raw)
In-Reply-To: <201109071958.47945.jkrzyszt@tis.icnet.pl>

On Wed, 7 Sep 2011 at 19:58:47 Janusz Krzysztofik wrote:
> On Wed, 7 Sep 2011 at 13:47:40 Russell King - ARM Linux wrote:
> > On Wed, Sep 07, 2011 at 01:10:08PM +0200, Janusz Krzysztofik wrote:
> > > Any special requirements as to the process of submitting bug
> > > fixes against arch/arm common bits?
> > 
> > It needs to go into the patch system for merging so that it doesn't
> > get buried and forgotten - as already demonstrated.
> 
> Still not sure: am I suppposed to do something for the patch to go to
> the patch system? Or do you take care of this?

OK, instead of waiting for your answer, I've found an interface to your 
patch system myself and submitted the patch.

Next time, for how long after posting a patch to the linux-arm-kernel 
lists should I wait for comments before I can submit it to the patch 
system even if there are no signs of the patch being reviewed? IOW, can 
I assume you accept a patch if you don't comment it for a certain period 
of time?

Thanks,
Janusz

      reply	other threads:[~2011-09-08 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 11:07 Janusz Krzysztofik
2011-09-07 11:10 ` Janusz Krzysztofik
2011-09-07 11:47   ` Russell King - ARM Linux
2011-09-07 17:58     ` Janusz Krzysztofik
2011-09-08 18:02       ` Janusz Krzysztofik [this message]

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=201109082002.11635.jkrzyszt@tis.icnet.pl \
    --to=jkrzyszt@tis.icnet.pl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®