From: Will Deacon <will.deacon@arm.com>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: 'richard -rw- weinberger' <richard.weinberger@gmail.com>,
"'linux-arch@vger.kernel.org'" <linux-arch@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: A bug about system call on ARM
Date: Tue, 4 Jun 2013 09:48:32 +0100 [thread overview]
Message-ID: <20130604084832.GA27516@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D1610991B883@CNBJMBX05.corpusers.net>
On Tue, Jun 04, 2013 at 06:33:20AM +0100, Wang, Yalin wrote:
> Hi Will,
Hello,
> Could I know what's your git branch is mainly used for ?
>
> https://git.kernel.org/cgit/linux/kernel/git/will/linux.git
>
>
> I mean if the branch is used for ARM arch maintenance ?
I send most of my patches via Russell, and the tree above is where I keep my
patches whilst they're not yet in mainline.
> If yes, I think I can send future bugs about ARM to you directly,
> And do not need ping-pang in the mail list .
Quite the opposite! Having discussions on the mailing list is key to how the
kernel is developed, so please continue to send questions, bug reports and
patches there. As has been pointed out previously in this thread, you need
to choose the right list in the first place, rather than just sending to
LKML.
Of course, you can always CC me on arm/arm64 patches if you like.
Cheers,
Will
next prev parent reply other threads:[~2013-06-04 8:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 6:52 A bug about system call on ARM Wang, Yalin
2013-05-29 7:34 ` richard -rw- weinberger
2013-05-29 7:37 ` Wang, Yalin
2013-05-29 8:24 ` Wang, Yalin
2013-05-29 8:46 ` richard -rw- weinberger
2013-05-29 9:48 ` Will Deacon
2013-05-29 9:50 ` Wang, Yalin
2013-05-30 1:41 ` Wang, Yalin
2013-05-30 9:09 ` Will Deacon
2013-05-30 11:41 ` Will Deacon
2013-05-30 11:41 ` Will Deacon
2013-05-31 2:56 ` Wang, Yalin
2013-05-31 8:46 ` Will Deacon
2013-05-31 11:02 ` Wang, Yalin
2013-05-31 11:13 ` Will Deacon
2013-05-31 11:30 ` Wang, Yalin
2013-06-03 5:25 ` Wang, Yalin
2013-06-03 9:54 ` Will Deacon
2013-06-03 9:58 ` Wang, Yalin
2013-06-04 5:33 ` Wang, Yalin
2013-06-04 8:48 ` Will Deacon [this message]
2013-06-04 8:48 ` Will Deacon
2013-06-04 9:30 ` Wang, Yalin
2013-06-04 11:27 ` Will Deacon
2013-06-14 6:53 ` Wang, Yalin
2013-05-31 16:48 ` Nicolas Pitre
2013-05-31 16:52 ` Will Deacon
2013-05-31 3:54 ` Nicolas Pitre
2013-05-31 3:54 ` Nicolas Pitre
2013-05-31 8:45 ` Will Deacon
2013-06-03 10:18 ` Russell King - ARM Linux
2013-06-03 10:27 ` Will Deacon
2013-06-03 10:45 ` Russell King - ARM Linux
2013-06-03 12:39 ` Will Deacon
2013-05-29 8:54 ` Mikael Pettersson
2013-05-29 8:54 ` Mikael Pettersson
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=20130604084832.GA27516@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Yalin.Wang@sonymobile.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/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).