From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: Patches for ARC
Date: Mon, 27 Jun 2016 09:27:25 +0000 [thread overview]
Message-ID: <1467019584.3628.40.camel@synopsys.com> (raw)
In-Reply-To: <20160613203842.GF2584@waldemar-brodkorb.de>
Hi Waldemar,
On Mon, 2016-06-13@22:38 +0200, Waldemar Brodkorb wrote:
> Hi Alexey,
> Alexey Brodkin wrote,
>
> >
> > Hi Waldemar,
> >
> > Just saw that new change for ARC ("arc: use generic lowlevellock",
> > http://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=1b49dc96d103e0151fee290d55cea55aa12c906d).
> >
> > Even though this is very nice to see fixes and improvements done by people
> > outside Synopsys IMHO it still makes sense to add SNPS people in the loop so
> > we may review submitted patches.
> You are right, I first thought I need to add you, then I thought you
> are reading the low traffic list anyway.?
> Sorry for the trouble.
> ?
> >
> > So could you please first get an Ack from either Vineet (in Cc) or me before
> > committing stuff for ARC? Alternatively just Cc?linux-snps-arc at lists.infradead.org.
> I will do in the future. Do you thing following patch would be okay
> to commit to make changes to architecture specific parts
> more formal?
> ?
> >
> > Again I'm very happy with uClibc-ng and appreciate a lot all your efforts
> > and to make uClibc-ng more robust let's review stuff together.
> >
> > Also it was hard for me to find a relevant patch on the mailing list
> > because I was expecting patch to be sent via git "send-email" (which I think
> > should be a standard way for patch submissions in uClibc). Only going through a relevant
> > thread for ARM I found a message with attached files.
> Is the commit okay or do I need to revert it?
Sorry for late reply.
Yep this commit is fine so no need to do anything here.
-Alexey
prev parent reply other threads:[~2016-06-27 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 12:17 Patches for ARC Alexey Brodkin
2016-06-13 20:38 ` Waldemar Brodkorb
2016-06-14 7:13 ` Max Filippov
2016-06-27 9:27 ` Alexey Brodkin [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=1467019584.3628.40.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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).