Fix RIL_Init ending unexpectedly when passed unknown args.

When libsec-ril receives an unknown argument, RIL_Init completely aborts early.

With Android 5.0 and up, a "client id" argument is passed (via '-c' param),
but libsec-ril's getopt call uses "p:d:s:", and anything not '-p' '-d' or '-s'
jumps to the end of RIL_Init.
By passing '--' before '-c', getopt ignores what's left and signals it's done.

Currently there's no extra args passed after rild.libargs other than '-c',
but even if that were to change in the future this change would still be
required for RIL_Init to work.

Conflicts:
	system.prop

Change-Id: I904d1c7fd83c71f1c2e1961ed96ac698a160f7f9

0 files changed, 0 insertions, 0 deletions