[PATCH linux] net/ncsi: Fix possible deadlock caught with lockdep
Patrick Williams
patrick at stwcx.xyz
Fri Mar 4 09:35:18 AEDT 2016
On Mon, Feb 29, 2016 at 11:30:58AM +1030, Joel Stanley wrote:
> On Mon, Feb 29, 2016 at 8:38 AM, Cyril Bur <cyrilbur at gmail.com> wrote:
> > On Fri, 26 Feb 2016 17:09:40 +1030
> > So that is the preferred workflow? Happy to not do pull req but I've sortof
> > just gone with the majority.
>
> Yes. Doubly so for kernel patches (I'm the maintainer of that repo).
>
> We want the project to use the same workflow as most of the other
> projects that open source developers are familair with; xorg, kernel,
> skiboot, etc.
>
> I think the reason we're using the github -> mailinglist bridge is
> down people on the project not having access to real email servers
> they can use with git send-email.
>
The other reason is that many of the repository 'maintainers' use the
Github merge button instead of manually applying the patches in their
git repository and uploading. For the non-kernel repositories it is
much more convenient and easier to track if they are in a PR.
> > There's simply no way with stuff coming from GitHub? I find myself misreplying
> > to a lot of those...
>
> The github to mailing list bridge is Patrick's work. I suggested to
> him that we pull the author's name from patches and cc them; he's
> added it to his list.
I actually had it that way at one point and then started getting too
many bounces with people that either hadn't properly 'git-config
user.email'd or edited in Github directly which scrubs the commit author
email. I'll have to think about the best way to detect that so my bot
doesn't get tons of bounces.
>
> Cheers,
>
> Joel
> _______________________________________________
> openbmc mailing list
> openbmc at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
--
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160303/674b217a/attachment.sig>
More information about the openbmc
mailing list